seerr_flush_cache

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

Annotations already indicate readOnlyHint=false, so the description's 'WRITE: this modifies your Seerr instance' adds context about the mutation but is largely redundant. It does not disclose additional behavioral traits such as side effects, reversibility, or prerequisites beyond the basic write operation.

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 entire description is one concise sentence that front-loads the action and uses a clear structure. Every word contributes to understanding the operation, with no superfluous content.

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 one-parameter tool, the description is adequate but lacks essential guidance on obtaining cache_id (e.g., referencing seerr_list_settings_cache). The output schema exists but its content is unknown, so return value details are not covered, but the missing parameter context leaves a gap.

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?

With schema description coverage at 0%, the description does not explain what cache_id is, its format, or how to obtain valid values. The phrase 'specific cache' hints at the parameter but provides no substantive meaning beyond the schema's type and required status.

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 'Flush a specific cache' clearly states the action (flush) and resource (specific cache), distinguishing it from sibling seerr_flush_dns_cache and seerr_list_settings_cache. The verb and resource are specific and unambiguous.

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 the tool is for flushing a particular cache identified by cache_id, but it does not explicitly state when to use it versus alternatives like seerr_flush_dns_cache or how to discover valid cache IDs. There is no exclusion or alternative stated, only an implied context.

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