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

Annotations already declare readOnlyHint and idempotentHint. The description adds value by disclosing that authentication is required and that the tool produces no acceptance/payment side effect, with those actions deferred to an external site.

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 sentences with no filler: purpose is front-loaded, the key behavioral constraint is next, and the auth requirement closes it. Every sentence earns its place.

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 single-parameter lookup tool with safety annotations, the description is largely complete: it covers purpose, external flow, auth, and non-mutation. It stops short of explaining the return format or possible failure cases, but this is minor given the tool's simplicity.

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%, and the description does not mention quote_id at all. The parameter name is self-explanatory, but the description fails to compensate for the schema's lack of explanatory context, such as where to obtain the quote_id.

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 specific verb and resource: 'Look up a quote and return a deep link.' It clearly differentiates itself from action-oriented siblings by explicitly saying it 'deliberately does not accept or pay,' and the title reinforces the deep-link scope.

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 gives clear usage context: quote acceptance and payment happen on tewdy.com via the deep link, not in chat. This tells the agent when not to attempt acceptance/payment in chat, though it does not explicitly name alternative sibling tools for those actions.

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