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

Annotations already declare destructive=true, readOnly=false, idempotent=false, so the safety profile is structured. The description adds important behavioral context: confirmation requirements for generated replacements, the preview/confirm workflow, and the instruction to follow the response envelope's primary nextAction. It does not enumerate the specific destructive effect of each operation, which keeps it from a 5.

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 front-loaded with purpose and confirmation guidance, then operation scope, then return/envelope behavior. The long operation list duplicates the schema enum, which is somewhat redundant, but it also communicates the tool's breadth in one place. Overall it is appropriately sized for a 19-operation umbrella tool.

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?

Given 50 parameters, nested objects, an output schema, and destructive annotations, the description covers the critical context: operation scope, confirmation workflow, contracts resource, guided_turn fallback, and response envelope handling. It is not a full operation-by-operation guide, but the schema and output schema carry the detailed contract and the description fills the high-level gaps.

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 schema already documents all 50 parameters and a baseline of 3 applies. The description meaningfully adds beyond the schema by explaining the contracts resource for typed paths/values, the guided_turn fallback for missing facts, and the confirm:false-then-confirm:true preview pattern. It does not explain individual parameters, but it adds useful semantics for the highest-risk fields.

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 states a specific verb and resource: editing a saved document or application via a selected operation. It lists all operation families, making it clear that this is an umbrella edit tool rather than a create/delete tool. It does not explicitly contrast with siblings like create_item or delete_items, so it falls short of a 5.

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?

It gives concrete usage guidance: use confirm:false for preview, then repeat with confirm:true after user confirmation; generated replacements require conversation confirmation; document field edits should read democruit://contracts/{memberTool} or use guided_turn. It lacks explicit when-not-use guidance and does not route between all sibling edit/alternative tools, but the context is clear.

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