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

Goes well beyond the destructiveHint/openWorldHint annotations by disclosing that deletion is recoverable, that owners require an active Pro subscription while permitted collaborators do not, and that the main API enforces trip membership and edit permissions. The untrusted-content warning and closed-world scope statement add real operational context an agent would not otherwise have.

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 action and parent-selection rule are front-loaded and easy to scan. The trailing safety block partly restates the annotations (closed-world, destructive), which is mild redundancy but short enough not to obscure the operative guidance.

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 destructive, permission-gated delete with an output schema and full annotation coverage, the description supplies everything an agent needs: recoverability, subscription/permission rules, parent targeting, and a prompt-injection caution. Return values are covered by the output schema, so nothing material is missing.

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 coverage is 100% so the baseline is 3, but the description adds meaning the schema does not: which parent to supply (the exact parent from the list result, not the trip) and why trip lists behave differently. It clarifies the otherwise ambiguous parent_id/parent_type relationship in practice.

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?

States a specific verb and resource ('Recoverably delete a document') plus the scope ('directly attached to the specified trip or itinerary parent'), which distinguishes it from documents_attach, documents_update, and the various *_delete siblings by parent type. An agent can identify the operation without opening the schema.

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?

Explicitly tells the caller to supply the exact parent_type and parent_id from the list result for child-object documents, and the schema-independent context (trip lists aggregate attachments) reinforces when the parent parameters are needed. It does not name a specific alternative tool to use first (e.g. tripsy_documents_list), so it stops short of full routing guidance.

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