clear_old_cache

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

With no annotations provided, the description indicates a destructive action (clearing cache) and mentions the return value (status with count). However, it lacks details on side effects (e.g., impact on other users, reversibility) or safety considerations beyond 'expired' entries.

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 concise with a clear one-liner followed by structured args/returns. It could be even more concise but is well-organized and readable.

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?

Given the tool's simplicity (single parameter, output schema exists), the description covers its core function and return value adequately. However, it does not elaborate on edge cases or behavior when no entries are expired.

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 description adds meaningful context for the only parameter, 'max_age_minutes', beyond the schema's type and default, explaining it as 'Maximum age in minutes before considering expired'. This compensates for the 0% schema description coverage.

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 tool action ('Clear expired weather cache entries') with a specific verb and resource, distinguishing it from sibling read tools like get_alerts, get_current_time, and get_forecast.

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 implies usage for cache maintenance but does not explicitly state when to use this tool over alternatives (e.g., after forecast fetches) or provide any usage restrictions or prerequisites.

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