Get provider rates

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

The annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds meaningful context by explaining the two pricing structures (flat-priced per-check options vs plan-priced monthly plans) and the anonymous endpoint nature, which is valuable beyond annotations.

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 sentences, zero waste. Front-loaded with the purpose, followed by useful explanatory detail about pricing models and the no-scope requirement. Every sentence earns its place.

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 zero-param, read-only list endpoint with no output schema, the description explains what's returned (rate cards), the two pricing models, and the access model (anonymous). This is complete for the tool's simplicity level; no output schema means the return format responsibility is minimal.

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?

With 0 parameters and 100% coverage, the schema is trivially complete. The description establishes no parameters are needed ('Anonymous endpoint; no project scope needed'), which is the entire story for parameter semantics. This fully compensates for the zero-param case, warranting baseline 4 as per the rubric.

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 'List public provider rate cards used for rank-check cost estimates' with a specific verb, resource (rate cards), and purpose. It distinguishes between sibling tools by clarifying it's about cost-estimate rate cards and mentions 'Anonymous endpoint; no project scope needed' which differentiates it from get_cost_estimate and provider-related 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 specifies when this applies (for rank-check cost estimates) and clarifies no project scope is needed, which helps the agent know there's no prerequisite. It implicitly distinguishes from get_cost_estimate by noting this lists rate cards rather than computing an estimate, though it doesn't explicitly name the alternative tool.

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