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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds genuine context: deletion is permanent and cascades to associated view records. It also flags the confirm=true guard, which is the key behavioral gate for invoking it.

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?

Two short sentences, front-loaded with the irreversible action and cascade effect. No filler.

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 two-parameter mutation whose safety profile is already covered by annotations, the description supplies the two missing facts an agent needs: permanence and the cascade to view records. It stops short of failure semantics or permission requirements, but nothing essential to a correct call is absent.

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 0%, so the description carries the parameter burden. It only restates the confirm constraint that the schema already enforces via const:true, and says nothing about what 'id' identifies (the brief's UUID) or the consequences of an unknown/invalid id.

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?

Names a specific verb and resource ('Permanently delete a brief') and adds the cascade scope ('and its associated view records'), which distinguishes it from read/update siblings. The only nit is the naming mismatch between the tool id (delete_document) and the description's term 'brief', but 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?

No statement of when to use this vs. alternatives, no prerequisites about ownership/permissions, and no warning about irreversibility beyond the word 'permanently'. The only usage note (confirm must be true) is already enforced by the schema.

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