clear_bioportal_cache

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

No annotations are provided, so the description carries full burden. It discloses that the tool clears the entire cache and returns a dictionary with cleared_count. However, it does not mention any potential side effects, permissions required, or behavior if the cache is already empty. Given the simple destructive nature, this is acceptable but not rich.

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 short and front-loaded, with the core action stated in the first sentence. Subsequent sentences add usage context and return information without redundancy. Every sentence 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?

This is a simple tool with no parameters, and the description covers the action, the rationale for use, and the return value. It is complete for its intended scope and no additional information is necessary.

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, so the schema fully covers expectations with an empty object. Per the baseline rule, a score of 4 is appropriate since there is no parameter information to add.

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 opens with a specific verb and resource: "Clear all entries from the BioPortal search cache." This clearly distinguishes it from the sibling tool remove_stale_cache_entries, which targets only stale entries, by specifying the full scope of action.

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 explicit use context: "force fresh API calls for all subsequent BioPortal searches" and "useful when ontology data has been updated." It does not explicitly mention the alternative remove_stale_cache_entries or state when not to use it, but the context is clear enough for most scenarios.

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