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

Annotations indicate non-readOnly and non-destructive, and the description adds that the tool changes status from 'unapproved' to 'draft'. However, it does not disclose potential side effects, error conditions, or whether reversible. Adequate but not detailed.

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, concise sentence that captures the essential action without unnecessary words. It is front-loaded and efficient.

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 a single parameter and the existence of an output schema, the description adequately explains the state transition. It could mention error conditions or required permissions, but for a simple toggle operation, it is largely complete.

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?

With 0% schema description coverage, the burden on the description is higher, but the single parameter (deliverable_id) is self-explanatory from the tool name and description. No additional context is provided beyond the schema, so it meets the minimum but does not exceed.

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 clearly identifies the verb ('return') and the resource ('unapproved review deliverable' to 'editable draft status'), distinguishing it from sibling tools like approve_consulting_deliverable or submit_consulting_deliverable.

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 description implies the tool is used when a deliverable is unapproved and needs to be reverted to draft, but it does not explicitly state when to use it versus alternatives or mention prerequisites (e.g., the deliverable must be in 'unapproved' state).

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