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

Annotations declare destructiveHint=true, which signals the operation may overwrite or destroy existing data. The description adds nothing about what gets destroyed, whether the edit is reversible, what permissions are required, or what happens during an edit. With annotations covering only part of the safety profile, the description should carry more weight but does not.

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 a single, efficient sentence that front-loads the action ('Edit...'). It is appropriately sized with no wasted words, though it is arguably too terse for the tool's complexity.

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?

There is no output schema, no additional behavioral context, and no parameter explanations. For a destructive mutation operation with five parameters and zero schema descriptions, the description is insufficient to guide correct invocation. It should explain what can be edited, what the destructive hint implies, and how it relates to approval and submission tools.

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 must compensate for five undocumented parameters. The description names no parameters at all, leaving the agent to infer from the schema that title, due_date, description, milestone_id, and deliverable_id are editable fields. It mentions 'internal draft deliverable' but does not clarify what aspects can be edited. This is inadequate for a 0% coverage schema, but the schema itself includes type and format info that partially compensates.

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 says 'Edit an internal draft deliverable', which is a specific verb (edit) and resource (deliverable). However, it does not distinguish this tool from close siblings like update_consulting_document_revision, submit_consulting_deliverable, or approve_consulting_deliverable, which all operate on consulting deliverables/documents. The scope is clear but sibling differentiation is missing, which caps this at 3.

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 phrase 'review/approval state is separate' implies that this tool should not be used for approval actions and that approval is handled elsewhere, which gives some usage context. However, there are no explicit when-to-use or when-not-to-use guidelines relative to alternatives like submit_consulting_deliverable or update_consulting_document_revision. This is only implied usage guidance.

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