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

With no annotations, the description carries the full burden. It discloses the cache auto-expiry TTLs and describes actions. However, it lacks details on side effects, such as potential performance impact or irreversible nature of flush_all, beyond calling it 'nuclear clear'.

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 paragraph that quickly states the purpose, lists actions, and gives example calls. It is front-loaded with key information, though it could be slightly more structured for readability.

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 two parameters (one required) and full schema coverage, the description covers core functionality and TTL details. However, with no output schema, it omits return format or possible errors, which would aid an AI agent in interpreting results.

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%, but the description adds value by providing concrete call format examples (e.g., tokendiet_cache({ action: 'stats' })) and clarifying the allowed values for 'action' and the role of 'tool' parameter. This exceeds mere schema repetition.

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 it manually triggers or inspects the TokenDiet smart cache, listing three specific actions (stats, flush_tool, flush_all). This distinguishes it from all sibling tools, none of which are cache management tools.

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?

Description provides context for each action (stats shows live cache entries and hit counts, flush_tool clears cache for one tool, flush_all is nuclear clear) and mentions auto-expiry per tool TTL. It does not explicitly state when not to use, but the guidance is clear.

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