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

Annotations already flag destructiveHint=true, openWorldHint=true and idempotentHint=false, so the safety bar is lower. The description adds meaningful context beyond them: escalate spends from the buyer balance and requires public_input_acknowledged (true), hinting that input becomes publicly visible. It does not explain reversibility, what install overwrites, or why idempotency_key matters for a non-idempotent operation.

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?

It is compact and front-loads the three actions, but it is written as telegraphic REST endpoint listings (GET/POST paths) that add little for an MCP caller and reduce readability. Every line does carry some information, so nothing is bloated, but the structure is machine-doc shorthand rather than agent-facing prose.

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 11-parameter, destructive, open-world tool with no output schema, the definition is thin: it never says what fallback wiring is, what read/install return, what a fallback order commits the buyer to, or what happens on failure. An agent could invoke it but would be guessing about consequences.

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 only 9%, so the description must compensate, and it does partially by enumerating the escalate body fields (need, budget_usd, callback_url, idempotency_key, public_input_acknowledged, optional via_integration). But eight top-level parameters — token, handle, delete_credential, payment_signature, wanted_id, transfer_id, id, agent_key — remain unexplained anywhere beyond the schema's terse 'required by action' note.

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 names three concrete operations on a specific resource: reading/installing fallback wiring and opening a fixed-price fallback order against the buyer balance. The verb-to-action mapping (escalate = open a fixed-price fallback order) is spelled out, so an agent can tell what each action does. It does not, however, distinguish this from the similarly named sibling request_escalate or contract_recovery.

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?

There is no guidance on when to choose read vs install vs escalate, no prerequisites (balance, agent registration), and no mention of alternatives such as request_escalate. The action list describes what each branch does mechanically, but selection criteria are left entirely to inference.

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