Update Tool Call Accuracy to output unified format

[m7md7sien]

Description

Update Tool Call Accuracy to output unified format

If an SDK is being regenerated based on a new API spec, a link to the pull request containing these API spec changes should be included above.

All SDK Contribution checklist:

• The pull request does not introduce [breaking changes]
• CHANGELOG is updated for new features, bug fixes or other significant changes.
• I have read the contribution guidelines.

General Guidelines and Best Practices

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

[Copilot]

Pull request overview

This PR updates the Tool Call Accuracy evaluator to emit a more unified result format (e.g., *_score, *_properties, *_status) and aligns unit tests and the underlying prompty schema accordingly.

Changes:

• Updated the Tool Call Accuracy prompty contract to output reason, score, status, and properties (including a new “skipped” status behavior).
• Updated ToolCallAccuracyEvaluator to map prompty output into the unified SDK result shape (adds *_score, *_properties, *_status, *_passed, while keeping legacy keys for compatibility).
• Updated unit tests to assert against the new unified output keys and “skipped” behavior.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
sdk/evaluation/azure-ai-evaluation/tests/unittests/test_tool_call_accuracy_evaluator.py	Updates mock prompty outputs and assertions to use *_score/*_properties and new skipped behavior.
sdk/evaluation/azure-ai-evaluation/tests/unittests/test_agent_evaluators.py	Updates ToolCallAccuracyEvaluator expectations to reflect skipped results (score/properties None, status skipped).
sdk/evaluation/azure-ai-evaluation/azure/ai/evaluation/_evaluators/_tool_call_accuracy/tool_call_accuracy.prompty	Renames output fields and adds a “skipped” status contract.
sdk/evaluation/azure-ai-evaluation/azure/ai/evaluation/_evaluators/_tool_call_accuracy/_tool_call_accuracy.py	Implements unified output formatting, status handling, and properties packaging.
sdk/evaluation/azure-ai-evaluation/azure/ai/evaluation/_evaluators/_common/_base_prompty_eval.py	Adds a helper to return unified “not applicable/skipped” results.

Comments suppressed due to low confidence (1)

sdk/evaluation/azure-ai-evaluation/azure/ai/evaluation/_evaluators/_tool_call_accuracy/_tool_call_accuracy.py:241

• _convert_kwargs_to_eval_input never includes a response field in eval_input, so _is_intermediate_response(eval_input.get("response")) and the subsequent response preprocessing are effectively dead code and won't prevent evaluating intermediate assistant messages. Consider moving the intermediate-response check to _real_call (using the original kwargs["response"]) or removing these branches if response is not part of the prompty inputs.

        # Check for intermediate response
        if _is_intermediate_response(eval_input.get("response")):
            return self._return_not_applicable_result(
                "Intermediate response. Please provide the agent's final response for evaluation.",
                self.threshold,
            )

        # Preprocess messages if they are lists
        if isinstance(eval_input.get("response"), list):
            eval_input["response"] = _preprocess_messages(eval_input["response"])