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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=false. The description adds useful behavioral context beyond that: the quote is expiring, it does not dispatch the provider, and it requires obtaining spending authorization before proceeding. No contradiction with 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?

Three tightly written sentences, front-loaded with the core purpose and behavior. Every sentence adds information: purpose, non-dispatch constraint, and the required authorization workflow.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. The description completes the workflow context well, but it omits any parameter guidance, leaving the viewport enum and checklist usage under-documented for a tool with 50% schema coverage.

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?

The description mentions no parameters at all. With only 50% schema description coverage and the viewport enum lacking a description, the description fails to compensate for the gaps, leaving an agent to rely solely on the partial 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?

States a specific verb+resource ('Prepare an expiring AI-credit quote for hosted page assessment') and explicitly disambiguates from the sibling review_page by noting it does not dispatch a provider. An agent can immediately tell this is a preparatory quote tool, not the actual review.

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?

Clearly positions itself as a prerequisite step: 'Show the quoted cost and obtain spending authorization before review_page.' This gives clear context for when to use it relative to review_page, though it does not state when not to use it or name other alternatives.

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