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

Annotations indicate it is not read-only, not idempotent, and not destructive, but the description adds a meaningful nuance: 'internal draft' implies the deliverable is not final or client-facing. However, it does not disclose permission requirements (what 'owned' entails), side effects of creation, or any other behavioral details. The description adds some value beyond annotations but remains thin.

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, compact sentence that front-loads the action ('Create') and the key qualifiers ('internal draft deliverable', 'owned engagement'). There is no filler or redundancy; it is as concise as possible while still conveying basic purpose.

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 the tool has 6 parameters (3 required), no output schema, and generic annotations, the description is far too brief to be complete. It does not explain the meaning of 'internal draft', the concept of 'owned engagement', or any expected behavior. An agent would struggle to decide when to use this tool versus alternatives like 'update_consulting_deliverable' or 'create_consulting_document_revision'.

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 the lack of param explanations. It only hints that 'engagement_id' relates to an 'owned engagement', but does not clarify the required 'key' (a pattern string) or 'title', nor the optional fields. Since the schema provides no descriptions at all, the tool description leaves the agent with almost no semantic guidance for parameters.

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 states a specific verb ('Create') and resource ('internal draft deliverable'), and adds context ('on an owned engagement'). This distinguishes it from sibling tools like 'approve_consulting_deliverable' or 'submit_consulting_deliverable' by hinting at a draft state, but it does not explicitly name any alternative or contrast. It is not a tautology and conveys the main purpose effectively.

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 gives no guidance on when to use this tool versus alternatives. It does not mention conditions, prerequisites, or contexts (e.g., 'Use when the engagement is owned by you and a draft is needed'). No exclusions or sibling references are included, leaving the agent to infer usage from the name alone.

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