clear_cache

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

No annotations provided, so description must disclose all behavioral traits. It states it removes repos older than max age, but does not mention whether removal is permanent, whether confirmation is required, or any prerequisites (e.g., workspace must exist). Lack of destructive/reversibility info is a gap.

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?

Two concise sentences that front-load the main action ('Purges old cached repositories') and then specify the condition (older than max age). No extraneous information.

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?

No output schema, so description should explain return value (e.g., count of removed repos, success status). Without that, agent cannot determine how to proceed after invocation. Otherwise, adequate for a simple purge operation.

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 coverage is 100% with descriptions for both parameters. Description adds minimal value beyond schema (e.g., default for maxAgeDays), but does not provide further clarifications like format or constraints.

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?

Clearly states it purges old cached repositories from the .docsgrep workspace, specifying the exact resource and action. Differentiates from sibling tools like 'check_stale' which checks for staleness but doesn't purge.

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?

Implies usage for cleanup after analysis (e.g., after running analysis tools), but does not explicitly state when to use this tool versus alternatives (e.g., manually deleting files) or when not to use it (e.g., if repos are still needed).

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