send_draft_order_invoice

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

No annotations are provided, so the description carries full burden. It discloses that an invoice email is sent with a secure checkout link, but it does not mention side effects, state requirements (e.g., draft order must be in a certain state), idempotency, or response behavior. For a mutation tool, this is insufficient.

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 one sentence, concise and to the point. It front-loads the essential action. However, it could be slightly expanded with usage context without sacrificing conciseness. Thus, 4.

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?

For a mutation tool with 5 parameters, no annotations, and no output schema, the description is too minimal. It lacks details on when to use, prerequisites, return behavior, and error conditions. A tool like this should provide more context for an AI 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 100% with 5 parameters all described. The description adds 'secure checkout link' context but does not elaborate on parameter meaning beyond what the schema provides. Baseline 3 is appropriate as the schema handles parameter semantics adequately.

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 action: 'Send an invoice email for a draft order with a secure checkout link.' It uses a specific verb ('Send') and resource ('draft order invoice') and distinguishes from siblings like 'complete_draft_order' by specifying the email sending aspect.

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?

No guidance on when to use versus alternatives. There are related tools like 'complete_draft_order' that might also send notifications, but the description does not clarify when to choose this tool or indicate any prerequisites or constraints.

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