rm_delete_approval

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

Annotations already mark this as destructive, and the description adds the crucial behavioral requirement that confirm=True must be passed. It also constrains deletion to 'pending' approvals, which provides meaningful behavioral context beyond the schema and 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 efficient sentence that front-loads the core action and resource before adding the essential confirm requirement. There is no wasted wording.

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 two-parameter destructive delete operation with an output schema and strong annotations, the description covers the main invocation requirement and target. It could be slightly richer regarding the consequences of deletion, but nothing critical is missing for basic correct invocation.

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 only clarifies the confirm parameter ('requires confirm=True'). The approval_id parameter is left entirely to the schema's type definition, with no guidance on format, source, or valid values.

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 action ('Delete') and a specific resource ('pending approval record'), which clearly distinguishes it from sibling deletion tools like rm_delete_holiday or rm_delete_time_entry. The parenthetical about confirm also adds immediate functional clarity.

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 a clear usage prerequisite ('requires confirm=True') but does not explicitly state when to use this tool versus alternatives such as rm_update_time_approval_status or other approval-related tools. The context is implied but not fully explicit.

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