get_agent_run_telemetry

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds the specific error condition 'agent_run_not_found' for unknown run_id, which is beyond what annotations provide. It also clarifies the return type (telemetry batches), though that's somewhat redundant with the purpose. The added error detail elevates it above baseline.

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?

Three sentences with no filler. The main action and scope are front-loaded, followed by a sibling reference, an error note, and a return statement. Every sentence adds value and the structure is efficient.

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 simple read-only nature, two well-documented parameters, and the annotations covering safety, the description is complete. It includes the error behavior and states the return type. No critical information is missing for an agent to correctly invoke this tool.

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 100%, with both 'run_id' and 'limit' fully described in the schema. The description does not add additional parameter-level semantics, which is acceptable given the schema's completeness. Baseline of 3 is appropriate.

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 clearly states the specific verb 'Fetch' and resource 'runtime telemetry batches recorded for one agent run', and explicitly differentiates from sibling query_agent_run_telemetry which searches across runs. An agent can immediately distinguish this tool from its siblings without needing to inspect schemas.

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?

It explicitly directs when to use the alternative query_agent_run_telemetry for cross-run searches, and also notes the error case for unknown run_id. This gives clear contextual guidance on when this tool is appropriate versus when to choose another.

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