compare-runs

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

Discloses rendering behavior as Apps SDK card (ChatGPT) or JSON text (Claude), which is useful context. No annotations provided, so description carries the burden and does well by highlighting client-specific output.

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?

Two concise sentences, front-loaded with purpose, 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?

With no output schema, description hints at output format (card/JSON), which is helpful. Could mention output more explicitly, but adequate for a comparison tool with 3 parameters.

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 100% of parameters with descriptions; description adds context that comparison is 'side-by-side', but doesn't add meaning beyond what schema provides.

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?

Description clearly states 'Side-by-side metric/param comparison across multiple runs' with specific verb and resource, and distinguishes from siblings like get-run and search-runs.

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?

Implies usage for comparison of multiple runs, but lacks explicit guidance on when to use this versus alternatives like search-runs or get-metric-history.

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