fetch_benchmark_results

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

No annotations provided; description only mentions download and return. Does not disclose authentication needs, rate limits, error handling (e.g., if run incomplete or missing), or whether artifacts are deleted.

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?

Single sentence with no filler. Front-loaded with key action and resource.

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?

No output schema; description mentions 'migration report with tokens/sec deltas' but not format or structure. Lacks details on error conditions or prerequisites.

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 covers both parameters (100% coverage). Description adds 'completed' qualification for run_id and restates schema info, but adds no meaningful extra beyond schema.

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?

Explicitly states verb 'Download', resource 'artifacts from completed arm-bench run', and output 'migration report with tokens/sec deltas'. Distinct from sibling tools that analyze workloads or plan migrations.

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?

Implicitly suggests use after a completed run, but no explicit 'when to use' or 'when not to use' guidance. No mention of alternatives like analyzing workload instead.

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