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

With no annotations provided, the description carries the full burden. It explicitly lists the return elements (tiers, price, currency, interval, etc.) and notes it's the same as /api/pricing.json. However, it does not disclose whether the data is cached or if it requires authentication, but for a read-only, zero-parameter tool, the behavioral detail is sufficient.

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 concise sentences that front-load the main purpose and provide a helpful reference to the equivalent API endpoint. No wasted words; every sentence adds value.

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 no output schema, the description compensates by enumerating the return fields (price, currency, interval, etc.). It could mention that the data is static or note any limitations, but for a simple catalog tool, it is largely complete. The sibling list is provided but not differentiated, which is acceptable.

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?

There are no parameters in the input schema, so the description has no need to add parameter semantics. Baseline 4 applies since the schema coverage is 100% and no parameters exist. The description correctly omits parameter details.

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 the tool returns the full paid-offer catalog with specific details (price, currency, interval, etc.). It distinguishes itself from siblings by noting it provides the same data as /api/pricing.json, making the purpose unmistakable.

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 implies usage for obtaining the complete pricing catalog, similar to a specific API endpoint. While it doesn't explicitly state when not to use it or provide alternatives, the context of siblings like get_payment_info suggests this is for the full catalog rather than individual records. Clear but lacks explicit exclusions.

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