lucky_delete_stun_rule

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

The annotations already communicate that the operation is destructive and idempotent, so the description's burden is lower. It adds only that the target is identified by key, and does not mention side effects, error behavior, or irreversible consequences beyond what annotations indicate. No contradiction with annotations.

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 clear sentence with no filler. It is efficient, though it sacrifices useful operational detail that would make it fully self-sufficient.

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 one-parameter delete operation with annotations covering destructiveness and idempotency, the core call is understandable. However, it is incomplete for an agent that needs to know how to discover a valid key or what happens when the key does not exist.

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 0%, so the description must compensate. 'by key' indicates the single parameter is an identifier, but it does not explain the key's format, how to get it, or any constraints, leaving meaningful ambiguity.

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 states a specific verb ('Delete'), a specific resource ('Lucky stun rule'), and the key-based identification. This is enough to distinguish it from the many sibling CRUD tools for other resources.

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 gives no guidance on when to use this tool versus list/create/update stun rules, how to obtain a valid key, or any prerequisites. The intended usage is only implied by the action verb and resource name.

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