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

Beyond readOnlyHint=true, the description discloses that results are ordered newest first and include links, both useful for interpreting and presenting the listing. It leaves result limits, pagination, and whether entries contain summaries or full article text unspecified.

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?

A single compact sentence front-loads the resource and subject, then efficiently adds ordering, links, and intended use. The parenthetical topic list is dense but informative, and there is no filler or repetition of schema details.

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 with one optional, fully documented parameter, the description supplies the source, subject matter, ordering, link availability, and a practical use case. Because there is no output schema, the lack of result-cardinality and article-entry field details prevents full completeness.

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 schema fully documents the sole optional lang parameter, including its allowed values and default of en. The description adds no further language-selection semantics, so the high schema coverage appropriately establishes the baseline score.

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 identifies the resource as AI Rate Card articles about AI model prices, including cheapest models by task, price moves, and costs. The focus on linked articles broadly distinguishes it from the pricing-oriented siblings, though it does not explicitly contrast article retrieval with any particular sibling.

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 phrase 'to quote or point a reader to' provides a concrete use case: finding citable or shareable articles. It does not explain when to use a sibling such as get_model_prices or cheapest_models instead for direct pricing data, but the intended context is clear.

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