delete_order

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

No annotations are provided, so the description must carry the full burden. It mentions 'permanent' which hints at irreversibility, but fails to disclose other behavioral traits such as authorization requirements, cascading effects on related data, or whether the operation can be undone. This is a significant gap for a mutation tool.

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 very short (one sentence), which is concise, but it is written in Danish while the tool name is English. This language inconsistency may cause confusion for non-Danish-speaking agents. The structure is front-loaded but lacks clarity for a multilingual audience.

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 that there is no output schema, the description should explain what the tool returns (e.g., success status, deleted entity). It does not. As a mutation tool with one parameter, it is minimal but incomplete for an agent to fully understand the tool's behavior.

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 input schema has 100% description coverage for its single parameter. The description adds no meaningful information beyond what the schema already provides ('Ordre ID der skal slettes'). With full schema coverage, a baseline score of 3 is appropriate.

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 'Sletter en ordre permanent' clearly states the action (delete) and the resource (order), with 'permanent' indicating irreversibility. This sufficiently distinguishes it from sibling tools like 'get_order', 'create_order', and 'update_order'.

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 explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites or when not to use it. However, the tool name and description imply it is for deletions, and the context of sibling tools (e.g., 'create_order', 'update_order') provides some implicit differentiation.

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