List prices

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

Annotations already declare this is a safe read-only operation. The description adds substantial behavioral context beyond annotations: it spends nothing, free tools cost 0, and each entry includes tool name, REST route, price lines, minimum_credits, or a formula when input-dependent.

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?

The description is front-loaded with the core purpose and cost behavior. The long sentence enumerating unit types and formula handling is dense but useful because there is no output schema to explain the returned entry structure.

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-parameter read-only catalog tool with no output schema, the description is complete enough: it explains what is returned, how prices are represented, how free tools appear, and when to use quote tools instead.

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 tool takes zero parameters, so parameter semantics are not a meaningful differentiator. Per the zero-parameter baseline, this is adequately handled by the schema and requires no parameter explanation in the description.

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 states a specific verb and resource: it lists what every Clipwright tool costs in credits. It also distinguishes this catalog/price-list function from sibling quote tools by explaining that exact paid-call numbers come from the quote tool named in each entry.

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?

It explains the central usage distinction: use this tool to see all prices, formulas, and free tools, but use the named quote tool for the exact number of a paid call. This directly routes the agent between list_prices and the quote_* siblings.

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