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

Annotations already declare idempotentHint=true, destructiveHint=false, readOnlyHint=false. The description adds genuinely new behavioral context beyond that: it does not invoke a model and does not approve final delivery, i.e. it is a draft-assembly step with no AI generation or sign-off authority. It stops short of stating what the assembled draft contains or how it relates to downstream review steps.

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 tight sentences with the operation front-loaded and the negative scope stated second. No filler, though the second sentence is somewhat terse relative to the complexity of the surrounding workflow.

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?

No output schema exists, so the description should ideally say what the resulting draft/review artifact is and what the caller does next. It covers the input precondition and the 'no model / no approval' boundary, but leaves the output side and downstream handoff to be inferred from siblings.

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 67% (projectId and idempotencyKey documented, title not). The description adds no parameter-level detail, so it neither compensates for the undocumented title field nor adds meaning beyond the schema. Baseline 3 is appropriate.

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?

States a specific verb+resource: 'Assemble a commercial deck review draft from a ready autofill artifact bound to the current analysis.' The source artifact is named, which helps distinguish it from generic produce_document or submit_draft siblings, though no sibling is explicitly named as an alternative.

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?

'From a ready autofill artifact bound to the current analysis' implies a precondition (an autofill must already exist and be bound), and 'does not ... approve final delivery' hints at the boundary of its scope. But there is no explicit when-to-use statement, no guidance on required prior steps, and no named alternative among the many deck/document siblings.

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