compare_isos

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

readOnlyHint already indicates safety; description adds return fields and constraints (2-4 max, ISO list). No contradiction.

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?

Efficient paragraph packs usage, example, params, return, exclusions. Could benefit from bullet points but no wasted sentences.

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 one param and no output schema, description fully covers usage, parameter details, and return structure. No gaps.

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?

Single param 'isos' is fully explained: comma-separated, 2-4 max, enumerated from 7 US ISOs, with example. Compensates for 0% schema coverage.

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?

Clearly states 'side-by-side of 2-4 ISO grids' with specific metrics, and distinguishes from siblings like get_grid_intelligence and get_grid_scoreboard.

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?

Explicitly says when to use (user wants side-by-side of 2-4 ISOs) and when not to (rank all grids or single-ISO deep brief), naming alternatives.

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