get_preset_pricing

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety profile is covered. The description adds one useful behavioral fact not in annotations: 'No token required,' which is relevant for unauthenticated access. It does not, however, describe caching, currency defaults beyond the schema, or response shape.

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 with the core purpose front-loaded, plus the endpoint hint and auth note. No wasted words, though it is arguably too terse to be maximally useful.

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 single-optional-parameter read-only tool with 100% schema coverage and clear annotations, the description covers purpose and the notable auth exemption. Since no output schema exists, return-value detail is not strictly required, though a hint about the pricing structure would help.

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 description coverage is 100%, so the currencies parameter is already fully documented with format ('EUR,USD') and default ('EUR'). The description's 'in given currencies' only restates what the schema provides, so the baseline 3 applies.

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?

Clear verb+resource combination: retrieves pricing for presets in specified currencies. Distinguishes itself as a pricing lookup rather than a preset listing, but does not explicitly differentiate from siblings like get_preset or list_presets, which could also be candidates for preset-related queries.

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?

No guidance on when to use this tool versus alternatives such as get_preset (preset details) or list_presets (available presets). The only contextual note is 'No token required,' which covers auth rather than tool selection.

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