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

Annotations already cover safety (readOnlyHint=true, openWorldHint=false), and the description adds real value by characterizing the payload: vendor pricing source and the date the price was checked, signaling point-in-time data with provenance. It stops short of describing behavior for an unknown id or whether all tiers are included.

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 front-loaded sentence with no filler; the key clause (what is returned) comes before the lookup-method clause. Every phrase carries information.

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 one-parameter read tool with annotations and no output schema, the description covers input form and the highlights of the returned payload. Missing are the not-found case and whether the tiers include currency/billing period detail, which matter for a pricing lookup with no output schema.

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 coverage is 100% and the description's 'by id (e.g. 'cursor') or name' essentially restates the agent parameter's own documented description without adding matching rules. With one fully documented parameter, the schema carries the semantic load, so 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?

The description names a specific verb and resource: fetching full pricing tiers for one AI agent or product, keyed by id or name, from AITeamGuide. It is clearly distinct from a bulk/cheapest listing, but it never names the sibling tools (search_ai_agents, cheapest_ai_agents) to make the boundary explicit.

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?

Usage is only implied: it is the tool for a known single agent, and the parenthetical id example suggests how to call it. There is no statement of when to prefer this over search_ai_agents (unknown id) or cheapest_ai_agents (comparison shopping).

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