actiond_cleanup

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

Explicitly warns of destructive and irreversible nature, reinforcing the destructiveHint annotation. Adds context about confirming intent, which is beyond the annotation.

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?

Well-structured with separate clauses for purpose, parameter usage, and warning. Slightly redundant with days=0 and all=true but overall concise.

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?

Explains return value (summary with deleted_jobs, deleted_dirs, retention window). Sufficient for operation without output schema.

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?

Parameter descriptions in schema already cover all and days fully. The description repeats these details without adding new semantics, so baseline 3 applies.

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?

States a specific verb (deleting), resource (terminal CI/CD jobs and artifact directories), and scope (done/failed/cancelled). Clearly distinct from sibling tools like job_cancel or job_retry.

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?

Provides usage guidance with default retention and parameter behavior (days=0 or all=true). Does not explicitly name alternatives but implies cleanup purpose. Includes caution to confirm intent.

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