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

Annotations already declare readOnlyHint=true, so the description carries a lower burden. It adds no behavioral details such as pagination behavior, sorting, or error conditions. The description's only behavioral clue is the cursor parameter, but it is not explained.

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 of approximately 10 words. Every word serves a purpose—no redundancy or fluff.

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?

Despite an output schema existing, the description is insufficient for a tool with 7 parameters and pagination. It does not explain cursor usage, how query interacts with other filters, or what the output represents beyond the schema. Sibling tools like 'search_news' indicate a need for clearer scope differentiation.

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% (all 7 parameters described in schema), baseline is 3. The tool description adds meaning for four parameters (provider, workload, context, price) beyond the schema's minimal descriptions, but does not cover limit, query, or cursor. The addition is marginal, maintaining the baseline.

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 'Search the pricing catalog with provider, workload, context, and price filters,' specifying the verb 'search' and the resource 'pricing catalog' with explicit filters. It distinguishes from siblings like 'benchmark_lookup' and 'calculate_cost' by focusing on searching and filtering, but does not detail the output.

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 like 'compare_models' or 'find_best_value'. The description only states what it does, lacking explicit when-to-use or when-not-to-use context.

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