delete_template

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

No annotations are provided, so the description must fully disclose behavioral traits. It states a destructive action ('Delete') but does not mention irreversibility, side effects (e.g., cascade deletion of associated data), or whether the environment or databucket must exist. This is insufficient for a deletion operation.

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 a single sentence of eight words, with no filler or redundant information. It is highly concise and front-loaded, earning its place without any waste.

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 simple delete tool with two parameters and no output schema, the description is minimal but adequate. It does not specify return behavior, error conditions, or consequences of deletion, which a more complete description would include. However, given the tool's simplicity, it meets a baseline level of completeness.

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 each parameter having a basic description (e.g., 'Environment UUID'). The description adds minimal value beyond the schema by indicating the operation's context, but it does not clarify parameter semantics further. Baseline 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 'Delete a databucket from a Mockoon environment' uses a specific verb (Delete) and resource (databucket), clearly distinguishing from sibling tools like delete_environment and delete_route which operate on different resources. The tool name 'delete_template' aligns with the description despite the synonym 'databucket', making the purpose unambiguous.

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, prerequisites, or conditions for deletion. It lacks explicit when-to-use or when-not-to-use context, leaving the agent to infer that it should only be used when intending to delete a databucket.

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