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

Annotations declare destructiveHint=true and readOnlyHint=false, which the description supports ('request a trade-in appraisal' implies a mutation). The description adds a key precondition ('after explicit consent and confirmation'), which is helpful. However, it does not disclose potential side effects (e.g., dealer contact being initiated) or the idempotency retry behavior, and does not explain what happens on dry_run or if the listing's seller is contacted automatically.

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?

Single sentence, front‑loaded with the critical prerequisite, zero wasted words. Perfectly concise.

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 an 18‑parameter, 10‑required, destructive toy with an output schema, the description is too brief. It does not explain the return contract (output_schema exists but gets no mention), does not clarify the idempotency guarantee, and does not specify which channel the appraisal request uses. While annotations and schema carry some burden, the description's extreme brevity leaves important behavioral questions unanswered.

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 61%, meaning 39% of parameters lack schema descriptions. The tool description compensates partially by stating the high‑level workflow (consent, then request), but does not individually clarify undocumented fields like trade_in_make, trade_in_model, trade_in_condition, or trade_in_trim. The warning 'never fabricate consent' in consent_text's description is valuable, but not part of the tool's description.

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 uses a specific verb-resource pair ('request trade-in appraisal') and clearly ties it to a 'listing'. However, it doesn't explicitly differentiate from siblings like 'submit_vehicle_inquiry' or 'schedule_test_drive', which also involve dealer actions.

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 provides no guidance on when to use this tool vs. alternatives. Given complex prerequisites (explicit consent, consent confirmation, listing ownership) and many sibling tools, the lack of when/why guidance is a serious gap.

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