passgage_delete_leave_rule

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

The description discloses that the operation is a delete, which is inherently destructive, but it does not mention any consequences such as irreversibility, cascade effects, or permission requirements. With no annotations to supplement, the description falls short of explaining the behavioral implications of the deletion.

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, concise sentence that delivers the essential information with no extraneous words. It is appropriately sized for a simple delete operation with one 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?

For a straightforward delete operation with one parameter and no output schema, the description is minimally adequate. However, it lacks any notes on permanence, side effects, or typical usage context, which would round out the picture for an agent deciding whether to invoke this tool.

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 schema alone describes the 'id' parameter as 'The UUID of the leave_rule to delete', covering its meaning fully. The description's phrase 'by ID' adds no new information beyond this, so it does not enhance the schema's parameter documentation. Given the high schema coverage, a baseline score of 3 is appropriate.

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 (Delete), the resource (leave_rule), and the key identifier (by ID). It effectively distinguishes this tool from sibling delete operations by naming the specific resource type, leaving no ambiguity about what it does.

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 or when not to use it. There is no mention of prerequisites, safety checks, or conditions that should be met before deletion. The usage is only implied by the obvious action described.

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