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

Annotations provide some behavioral hints (readOnlyHint=false, idempotentHint=false, destructiveHint=false, openWorldHint=false), but the description adds valuable context: acceptance records a choice, no work starts until payment, nothing owed until payment, quote must be unexpired, and a privacy warning against contact details. This goes beyond the annotations.

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?

The description is dense and front-loads the receipt_id requirement, but it's a bit of a wall of text with multiple conditional clauses. It could be structured with bullet points for clarity, though all sentences carry necessary 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?

Given the tool's complexity (4 params, nested objects, oneOf schema, no output schema, no annotations beyond basic hints), the description covers the essential workflow: pre-check via check_research_status, action-specific requirements, and post-acceptance effects. It could mention what happens after an action or response format, but it's largely complete.

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 0%, so the description must compensate. It explains the meaning and requirements of each action (confirm_scope, correct_scope, accept_quote, decline_quote), the need for receipt_id, when correction text is required, and that budget is a counter-offer. This meaningfully clarifies how parameters interact beyond the raw schema constraints.

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 a clear verb and resource: responding to SNTL's offer using a receipt_id, with four enumerated actions. However, it doesn't explicitly differentiate from siblings beyond mentioning check_research_status as a prerequisite, not as an alternative.

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?

It provides usage context: 'Use check_research_status before responding,' and explains the four actions and their requirements. It lacks explicit when-to-use vs. alternative guidance, though no direct alternative for responding exists.

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