cleanup_stale_analyses

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

No annotations are provided, so the description must fully disclose behavior. It says 'clean up' which implies deletion, but does not specify whether files are permanently removed, if there are any rollback capabilities, or what permissions are required. The lack of safety or side effect details reduces transparency.

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 sentence that immediately conveys the core purpose. It is appropriately sized and front-loaded, with no unnecessary words. Every word earns its place.

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?

The tool performs a destructive cleanup action but provides no output schema and no description of return values, success indicators, or side effects. An agent cannot determine what to expect after invocation. The description lacks completeness given the absence of 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?

Schema description coverage is 100%, so baseline is 3. The tool description adds little beyond the schema; it does not elaborate on parameter usage or relationships. However, the schema itself already provides adequate descriptions for both parameters (projectPath and maxAgeDays).

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 (clean up), the resource (stale analysis files), and the condition (older than specified days). It effectively distinguishes from sibling cleanup tools like cleanup_orphaned_projects and cleanup_stale_agents by targeting analysis files specifically.

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 no guidance on when to use this tool versus alternatives. It does not mention prerequisites, scenarios where it is appropriate, or when to avoid using it. Given the many sibling cleanup tools, this lack of context forces the agent to rely on tool names alone.

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