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

The description discloses the full side-effect profile: it creates an intake, returns a confirmation link, triggers contact policy (email/text/call), and details pricing with a card HOLD only after settlement improves. It also states 'never collect card details' and instructs to read customer_message verbatim. This goes well beyond the annotations (readOnlyHint=false, idempotentHint=true) by explaining the actual transaction flow and constraints.

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 long but dense and well-structured: it leads with the core purpose and minimum requirements, then details the output, contact policy, and pricing. Every sentence carries information necessary for correct usage (e.g., the $472 discount, the card HOLD condition, and the prohibition on card collection). It is appropriately sized for the complexity, though could arguably be tightened.

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?

With no output schema, the description fully explains the return value structure (customer_confirmation_url, customer_message, preliminary, contact_policy, pricing). It also covers operational edge cases (payment flow, who pays, when holds occur, notification options via notify_customer). An agent can act correctly without needing any additional context.

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 100% — every parameter already has an explanatory description. The tool description adds little beyond restating the minimum required fields (already implied by the schema's required array and the customer description) and summarizing output fields. It does not provide syntax or formatting details that the schema lacks, so the baseline of 3 applies.

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: 'Submit a vehicle owner's total-loss situation to SecondAppraisal on their behalf.' It clearly distinguishes this from the sibling tools (status, estimates, rules, uploads) by focus on submission. The intent is unambiguous.

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 context on when to use this tool: to submit a total-loss situation on behalf of a customer, with explicit minimum requirements (phone/email, agent self-ID, consent attestation). However, it does not explicitly contrast with alternatives or state when NOT to use it, so it stops short of a 5.

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