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

Annotations declare openWorldHint=true and idempotentHint=false, and the description adds meaningful context beyond them: a human must click a confirmation link before external providers are contacted, and 3+ providers are actually engaged. It does not warn about duplicate tickets on repeat calls (relevant given idempotentHint=false) or any rate limiting, which keeps it from 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?

Three dense sentences, front-loaded with what the tool does and immediately followed by the gating condition and the disqualifying cases. No restatement of the title and no filler.

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 16-parameter, non-idempotent, externally-facing tool with no output schema, the description covers purpose, prerequisites, exclusions, and roughly what comes back ('the reply lays every quote out on one 36-month basis'). The remaining gap is that it never explains how the many optional spec/incumbent fields should be populated.

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 only 6% across 16 parameters, so the description carries most of the burden. It clarifies a few high-value ones implicitly (work_email required, monthly_budget_usd via the $100/mo floor, category/quantity via the single-VPS exclusion, term_months via the 36-month basis), but gpu_model, gpu_count, incumbent_*, renewal_date, region, and notes get no explanation anywhere.

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 a specific verb and resource ('Opens a counter-quote request with the RentServers.com desk') plus the mechanism (3+ providers bidding blind, normalized to a 36-month basis), which clearly separates it from calculate_36_month_tco and get_server_price_index. It stops short of naming any sibling explicitly, so it is clear but not fully differentiated by routing language.

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 an explicit use condition ('Only call this when the user asks for quotes and provides their work email') and explicit exclusions ('Requests under $100/mo or for a single VPS get self-serve list prices instead of a ticket'). The confirmation-link gate is stated as a prerequisite before any provider is contacted, leaving nothing to inference.

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