delete_sales_document

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

Discloses that deletion only works on drafts (status != 0 fails) and that finalized documents need different handling. No annotations provided, so description carries full burden; missing mention of permanence of deletion, but still strong.

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?

Very concise: two sentences say everything needed. Front-loaded with purpose, no filler or repetition.

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 full schema coverage, output schema exists, and tool is simple, the description is complete. It covers purpose, constraints, and usage guidance adequately.

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 has 100% coverage, and description adds context: 'confirm' must be true, why only drafts can be deleted. Adds value beyond the schema's parameter descriptions.

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 the tool deletes draft sales documents, using the verb 'Delete' and specifying the resource. It distinguishes from siblings by noting that finalized documents cannot be deleted and must be voided via credit note.

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?

Explicitly states when to use: cleaning up unfinalised drafts, orphans, or experimental drafts. Also states when not to use: finalized documents, directing to credit note instead.

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