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

Annotations already establish this is a safe read-only operation. The description adds useful behavior beyond annotations: accepted formats, a 10 MB limit, and specific return information including detected product line, create_quote fields, and missing_required. It does not cover failure modes for unsupported or unreadable documents.

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 core purpose and workflow are front-loaded, but the description is dominated by lengthy purchase disclosure text unrelated to reading a declarations page. Most of the disclosure sentences do not earn their place in this tool definition and risk distracting the agent. The useful content could be much shorter.

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 read tool with no output schema, the description explains the return shape well, including missing_required. It also covers input constraints and the surrounding workflow with create_quote. The irrelevant purchase disclosures are excessive but do not prevent correct invocation.

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 schema describes email and document_base64, and the description adds file type and size constraints for the document. The optional filename parameter has no description in either the schema or the tool description, leaving a small gap. Overall, the description compensates reasonably for partial schema coverage.

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 opens with a specific verb and resource: reading a home or auto insurance declarations page. It also states accepted file types and what the tool returns, making the core purpose clear. Sibling differentiation is only indirect through references to create_quote.

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 a clear gathering order: ask for email, search email/files for a declarations page, send it to this tool, then pass returned fields to create_quote. The fallback of asking the consumer for create_quote fields is also stated. The later purchase-disclosure instructions are not relevant to invoking this read tool.

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