delete_order_note

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

The description adds the useful context that deletion is permanent, going beyond the destructiveHint annotation. However, it omits the nuance of the 'force' parameter, which in the schema states it must be true to permanently delete the note, making the behavior potentially misleading. It also does not describe any other side effects or response behavior.

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 consists of two short, front-loaded sentences that convey the operation and its irreversibility without any wasted words. Every word contributes to understanding.

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 description gives the core action and permanence but lacks important context such as the force parameter's role in permanent deletion, potential prerequisites (e.g., needing a valid order_id and note id), and what happens on success or failure. With no output schema, return values are not explained, but the omission of the force condition is a significant gap for a destructive operation.

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?

The description does not mention any parameters, but the input schema provides 100% coverage with descriptions for all four parameters (id, order_id, force, fields). According to the rubric, the baseline is 3 when schema coverage is high, and the description adds no extra parameter meaning.

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 specific action ('Delete') and resource ('a note from an order'), which directly matches the tool name and distinguishes it from siblings like create_order_note and list_order_notes. The addition of 'permanently removes' further clarifies the tool's 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 provides no guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or exclusions. The only hint is the word 'permanently', which implies caution but does not explicitly say when to choose this over other note-related tools.

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