cleanup_saved_logs

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

No annotations provided, so description must disclose behavioral traits. It mentions removal (destructive) but does not discuss reversibility, permissions, safety, or side effects (e.g., impact on other tools). Lacks transparency expected for a deletion tool.

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?

Single sentence of 18 words, front-loaded with the verb 'Remove'. No extraneous information, highly efficient.

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 tool with 2 optional parameters and no output schema, the description covers the basic purpose and modes. However, it lacks detail on behavior when both parameters are provided, the meaning of 'local', and whether the operation is reversible. Adequate but not fully comprehensive.

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%, so description must add meaning. It explains that 'buildRunId' identifies a build run and 'maxAgeHours' sets a retention window, and implies an either/or usage. However, it does not clarify edge cases (e.g., both parameters provided) or constraints (e.g., maxAgeHours limits).

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 (remove) and the resource (saved local log directories), and distinguishes two modes of operation (by build run ID or by age). No sibling cleanup tools exist, so differentiation is not needed.

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 two explicit use cases (removing logs for a specific build run or by age), but gives no guidance on when not to use, prerequisites, or alternatives. The mutual exclusivity of parameters is implied but not clarified.

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