rundeck_delete_job_executions

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

The description explicitly states the operation is irreversible, which is a key behavioral trait. However, with no annotations provided, it does not disclose other potential side effects, such as impact on running executions or permission requirements.

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 extremely concise at two sentences, with no superfluous information. Every word serves to convey the core functionality and a critical warning.

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 destructive operation with one required parameter, the description covers the essential action and irreversibility. However, it lacks detail about the return value (no output schema) and does not mention that the job must exist, but overall is adequate.

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 input schema already provides a description for the single parameter 'id' as 'Job UUID'. The tool description adds no additional semantic meaning beyond what the schema already provides, resulting in a baseline score.

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') and the resource ('all execution history for a job'), which effectively distinguishes it from siblings like 'rundeck_bulk_delete_executions' and 'rundeck_delete_job'.

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 given on when to use this tool versus alternatives, such as 'rundeck_bulk_delete_executions'. It also lacks any mention of prerequisites or context for use.

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