Drawing: Deliver Auditable Bundle

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

Annotations include destructiveHint=true, and the description adds useful behavioral context by naming result statuses ('success', 'failed_validation', 'failed_export') and stating that failure intentionally keeps all generated artifacts for diagnosis. However, it does not explain what destructive action may occur, such as overwriting files in output_dir or clearing prior bundles.

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 compact and front-loaded with the core function, followed by failure statuses and artifact-retention behavior. Every sentence adds useful information without repetition or filler.

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?

With a complete input schema and an output schema present, the description covers the essential operation, possible result statuses, and failure behavior. The remaining gaps—explicit destructive-effect disclosure and sibling differentiation—are partially covered by annotations and purpose clarity, so this is moderately 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?

Schema description coverage is 100%, so the input schema already documents all five parameters. The description adds no parameter-specific meaning beyond the schema, which keeps this at the baseline rather than higher.

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 opens with a specific verb and resource: 'Create a hashed, validated delivery bundle and verify DXF save/reopen parity.' This clearly distinguishes it from siblings like drawing_export_dxf, drawing_audit, and drawing_finalize, which do different work. The title 'Deliver Auditable Bundle' reinforces the purpose.

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 does not state when to use this tool versus alternatives such as drawing_export_dxf, drawing_audit, or drawing_finalize. It implies a final delivery/validation workflow but gives no explicit exclusions, prerequisites, or comparison with overlapping siblings.

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