sfc_delete_order

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

With no annotations, the description carries the burden. It discloses the confirm guard and a safety recommendation to search first, which is useful, but does not state that deletion is irreversible, what errors occur on invalid orderCode, or what is returned.

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?

Three short, front-loaded clauses with zero waste; the destructive action and its guard come first, and the recommendation follows.

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 two-parameter destructive tool with no output schema and no annotations, the description covers the essential guard and a pre-step but omits irreversibility and failure behavior, leaving meaningful gaps for a delete 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?

Schema coverage is 50%: confirm is already documented in the schema as 'Must be true to delete', and the description merely repeats it. orderCode, the undocumented parameter, is only identified as the key ('by orderCode') with no further format or lookup semantics.

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?

States a specific verb+resource: 'Delete an SFC order by orderCode'. It is clearly the only destructive/delete sibling among the listed tools, so it is distinguishable, though it does not explicitly contrast with siblings.

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?

Gives a prerequisite ('Requires confirm=true') and steers the agent toward an alternative action ('Prefer searching the order first'), effectively pointing at sfc_search_order. No explicit when-not guidance, but the pre-step recommendation is concrete.

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