delete_ability

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

With no annotations, the description carries the full burden for behavioral disclosure. It only says 'delete', which implies a destructive action, but does not state whether deletion is permanent, idempotent, cascading, or what happens when the ability does not exist.

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 short and wastes no words, but it is under-specified rather than usefully concise. It is essentially a restatement of the tool name and provides no structural information about parameters or usage.

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 destructive tool with no annotations, no output schema, and undocumented parameters, the description is insufficient. It lacks any mention of irreversibility, side effects, or related lookup tools, leaving an agent without enough context to call it safely.

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%, and the description does not mention or explain either parameter. The presence of 'id' and 'campaignId' as bare numbers is ambiguous; the description adds nothing to help an agent understand their roles or format.

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 an existing ability' is a direct restatement of the tool name 'delete_ability'. It names a verb and a resource, but adds no information beyond what the name already conveys, and does not distinguish it from the many sibling delete_* tools.

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 get_ability or update_ability. There are no stated prerequisites, exclusions, or suggestions for verifying the ability before deleting.

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