delete_approval

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

No annotations are provided, so the description carries full burden. It states the tool performs a deletion but doesn't disclose behavioral traits like whether this is irreversible, requires specific permissions, affects related data, or has rate limits. The description is minimal and lacks critical context for a destructive 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 appropriately sized and front-loaded, with the core purpose in the first sentence and parameter details in the second. There's no wasted text, and it follows a clear structure (general action followed by specific parameter).

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 tool's destructive nature, lack of annotations, and no output schema, the description is incomplete. It doesn't cover behavioral risks, success/error responses, or integration with sibling tools (e.g., how to obtain approval IDs). For a deletion tool with zero annotation coverage, this leaves significant gaps for an AI agent.

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 description adds meaningful semantics for the single parameter ('approval_id: Numeric ID of the approval to delete'), clarifying its purpose beyond the schema's basic type (integer). With 0% schema description coverage and only one parameter, this compensates adequately, though it could specify format constraints (e.g., positive integer).

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 clearly states the action ('Deletes') and resource ('an approval from a specified Storyblok space'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'delete_release_approval' or 'delete_access_token', which target different resources but share the 'delete' verb pattern.

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. It doesn't mention prerequisites (e.g., needing an approval ID from 'retrieve_single_approval'), exclusions, or compare it to similar deletion tools in the sibling list. The agent must infer usage from the tool name alone.

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