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

Annotations already indicate readOnlyHint=false, idempotentHint=true, and destructiveHint=true. The description adds the clarification that it 'Does not call a model or approve final delivery', which is additional behavioral context beyond annotations. However, it does not elaborate on the destructive nature (what gets overwritten) or idempotency semantics. Given the annotations, the bar is lower, and the description provides some extra clarity but not comprehensive transparency.

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 two sentences with no fluff. The first sentence defines the core purpose, and the second adds important constraints. It is front-loaded and every word serves a purpose. No redundancy or unnecessary detail.

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?

The tool has 3 parameters, no output schema, and annotations present. The description mentions the prerequisite ('ready autofill artifact') and clarifies what it doesn't do. It doesn't describe the return value or post-assembly steps, but since there is no output schema, that is not required. It could mention that the draft is not final or that it requires a valid current analysis, but overall it is sufficiently complete for an agent to invoke it correctly.

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 have good descriptions, but title lacks any description. The tool description does not mention any parameters or compensate for the undocumented title parameter. Since coverage is below 80%, the description should add meaning for uncovered params but does not, leaving title's purpose ambiguous.

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 action: 'Assemble a commercial deck review draft from a ready autofill artifact'. It also clarifies what it does not do ('Does not call a model or approve final delivery'), distinguishing it from related tools like build_autofill or submit_draft. The verb 'assemble' and the resource 'commercial deck review draft' give precise meaning.

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 usage after an autofill artifact is ready ('from a ready autofill artifact'), indicating it should be used after build_autofill. It also notes it does not approve final delivery, hinting that confirmation/submission tools are separate. However, it does not explicitly name alternatives or say when not to use it, so it lacks explicit exclusions, leaving room for improvement.

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