get_run

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

The description adds a performance warning about potentially large data, which goes beyond the readOnlyHint annotation. No contradictions were found.

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 extremely concise with two purposeful sentences: one for purpose, one for caution. No redundant information.

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?

For a simple read-only tool, the description covers purpose and a performance note. However, it lacks specifics about the returned 'detailed information' (no output schema). Overall adequate given tool simplicity.

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?

The description does not explain the 'run_id' parameter beyond the schema; it only implies its role via 'specific run'. With 0% schema description coverage, the description fails to add value for the parameter.

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 'Get detailed information about a specific run', specifying the action and resource. It distinguishes from sibling tools like 'get_runs' (plural) by implying single-run focus, but does not explicitly differentiate from other run-information tools.

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 advises 'avoid fetching many runs at once', indicating appropriate usage for single runs. It does not explicitly name alternative tools for batch retrieval, but the caution provides clear context.

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