remove_stale_cache_entries

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

With no annotations, the description carries the full transparency burden. It clearly states the destructive action (removing expired entries) and reassures that valid cached results are preserved. It also discloses the return dictionary. However, it doesn't mention permissions, failure modes, or whether the operation is reversible.

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 three concise sentences: the first states the purpose, the second adds usage context and TTL explanation, and the third describes the return value. Every sentence earns its place with no redundancy.

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 parameterless tool, the description fully covers purpose, usage scenario, and return value. It also provides enough distinction from the sibling clear_bioportal_cache. The presence of an output schema means the return dictionary does not need more detail.

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 tool has zero parameters, and the input schema confirms this. With no parameters to describe, the baseline is 4. The description adds no parameter documentation, and none is needed.

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's function: 'Remove expired entries from the BioPortal search cache.' It specifies the verb (remove), the resource (cache entries), and the scope (only expired), distinguishing it from the sibling tool clear_bioportal_cache, which would clear all entries.

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 a clear usage context: 'Use it to free disk space without losing valid cached results.' This indirectly differentiates it from a full cache clear, but it does not explicitly mention alternatives like clear_bioportal_cache or state when not to use this tool.

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