delete_middleware

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

No annotations are provided, so the description must fully disclose behavior. It merely states 'Delete' without explaining whether deletion is permanent, requires confirmation, or has side effects. The description lacks behavioral context beyond the obvious.

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 extremely concise with one short sentence. While it avoids verbosity, it sacrifices essential information. It could be expanded with a few words to improve clarity without harming conciseness.

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 the lack of annotations and output schema, the description is insufficient. It does not mention return values, error conditions, or the irreversible nature of deletion. For a deletion tool with many sibling operations, more context is needed to ensure correct usage.

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 only parameter, middleware_instance_name, is self-explanatory from its name. However, the description adds no additional meaning, such as format constraints or the need for the instance to exist. With 0% schema description coverage, the description fails to compensate.

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 uses the verb 'Delete' and the resource 'a middleware instance', clearly stating the action and target. Among sibling tools, there are other delete operations like delete_middleware_alert_rule, so it distinguishes by the type of resource. However, it does not specify the scope or effects of deletion.

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 is provided on when to use this tool versus alternatives such as backup_middleware or stop_middleware. There is no mention of prerequisites, conditions for safe deletion, or what to consider before invoking.

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