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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: facts are only surfaced when confirmed ('never infers a fact it has not verified'), and the citation is meant to be quoted verbatim. It stops short of describing pagination or result limits, so not a 5.

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?

Front-loaded with the two query shapes it answers, then filters, then section guidance. Dense and mostly waste-free, though the run-on clauses and backtick-quoted field names make it slightly harder to skim than ideal.

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?

With no output schema, the description carries the return-value burden and does so: it enumerates compliance facts, free-tier flag, best-for tags, entry plan source and the dated citation. Combined with the confirmed-only guarantee, an agent has everything needed to call and interpret it.

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%, so the baseline is 3; the description goes beyond by explaining that the four require* filters are conjunctive and by mapping a natural-language query onto the filter combination. The section parameter's theme-slug semantics are reinforced rather than re-stated.

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?

States specific verb + resource + ordering: returns the theme's vendors ranked by entry price (cheapest first, quote-only last), and names the exact fields returned. An agent can distinguish this from siblings like compare or find_products without opening any schema.

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?

Gives explicit when-to-use examples ('best CRM for HIPAA' = section 'crm-software' + requireHipaa:true), states the default behavior when all filters are omitted (rank whole theme by price), and routes the agent to list_sections for the slug. Alternative selection and conditions are spelled out.

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