Get Conversation Transcript

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and idempotentHint=true, so the tool's safety profile is known. The description adds value by enumerating the exact return contents (model_input, model_result, metric_value, scenario seed data) and noting it returns a 'complete' transcript. It does not contradict annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured and front-loaded: it opens with the main purpose, then gives usage context, then details the return values, and finally lists parameters in an Args block. Despite its length, every sentence serves a purpose and adds necessary detail that the schema omits.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simple retrieval nature, good annotations, and existing output schema, the description covers all necessary context: what it does, when to use it, how to select the target conversation, and what it returns. No additional information is needed for a competent agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description fully compensates by explaining all three parameters: test_run_id as UUID, scenario_index as a 1-based index visible in get_test_run_results, and test_id as an alternative UUID. This goes beyond the bare schema, which lacks descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action ('Retrieve the full conversation transcript') and a specific resource ('a single data point'). It clearly distinguishes itself from sibling tools like get_test_run_results by noting it is for drilling into a specific conversation after summary results.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says 'Use this after get_test_run_results to drill into a specific conversation,' providing clear context. It also explains how to identify the conversation (scenario_index or test_id) but does not explicitly mention when not to use the tool or name alternative tools for other purposes.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.