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

Beyond the annotations, the description discloses that the tool parses the PDF for specific fields, refreshes the preliminary estimate, and can take up to two minutes. This is meaningful behavioral context that the annotation flags alone do not provide. It does not contradict readOnlyHint or destructiveHint.

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, front-loaded with the action, then the parsing behavior, then the latency warning. Every sentence earns its place and no information is repeated from the schema or title.

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?

The description covers the essential operational facts for a state-changing async upload: what to attach, that a prior submission is required, what parsing and updates occur, and the two-minute wait. The exact response shape is not specified, but the description is sufficient for an agent to select and invoke the tool correctly.

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 input schema already documents all four parameters with full coverage, so the baseline is 3. The description adds genuine domain context by specifying the accepted report type (CCC / Mitchell PDF) and the data that will be extracted, which helps an agent choose the correct file to attach.

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 first sentence names a specific verb ('Attach'), a specific resource ('Market Valuation Report (CCC / Mitchell PDF)'), and a target ('submitted intake'). The parse-and-refresh detail further distinguishes it from the read-only sibling getters and from the initial submit_total_loss_intake tool.

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 clearly states that the tool applies to an already-submitted intake and implies the sequencing via 'submitted intake' and the need for prior submission tokens. It does not explicitly list exclusions or alternatives, but the context is clear enough for correct selection.

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