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

Annotations already declare readOnlyHint=true and openWorldHint=true, which are consistent with the description's mention of computing a quote and returning a URL without modifying data. The description adds useful context about pre-filling the booking form and the Stripe flow, enhancing transparency beyond 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 two sentences with no fluff. The first sentence packs the core functionality and output, while the second clarifies the user's next steps. Every word serves a purpose.

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 5 parameters (all described in schema), no output schema, and complexity of generating a signed URL, the description adequately covers what the tool returns and how it integrates into the user flow. It could mention error handling for invalid dates, but overall it's sufficiently 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 coverage is 100% with parameter descriptions. The description adds value by mapping 'dates, delivery option, and coupon' to specific parameters, explaining how they are pre-filled in the URL. This provides context beyond the raw schema.

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 clearly states the verb 'compute' and the resource 'price quote', and specifies the output as a 'signed checkout URL'. It effectively distinguishes the tool from siblings by detailing what the URL does (pre-fill dates, delivery option, coupon) and the subsequent user flow.

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?

The description implies usage after selecting a product and dates but does not explicitly state when to use this tool over siblings like propose_booking or check_availability. No direct comparison or when-not-to-use guidance is provided.

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