seerr_flush_dns_cache

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

Annotations already disclose that this is a write operation (readOnlyHint=false) and not destructive (destructiveHint=false). The description's 'WRITE: this modifies your Seerr instance' is largely redundant with the annotations and adds no additional behavioral context such as side effects, required permissions, or reversibility.

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 very short and front-loaded with the action, making it easy to parse. The 'WRITE:' prefix and following phrase are slightly redundant but still concise. There is no extraneous information, though the structure could be slightly more elegant.

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?

The tool is simple (one parameter) and has an output schema, but the description is incomplete for correct invocation. It omits what a DNS cache entry is, how to format the parameter, and any expected outcomes or side effects. This is a critical gap given the total absence of parameter descriptions in the schema.

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 description coverage is 0% for the only parameter, 'dns_entry'. The description does not explain what constitutes a DNS cache entry or what format is expected (e.g., hostname, IP address). The description fails to compensate for the missing schema detail, leaving the parameter ambiguous.

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 action ('flush') and the specific resource ('specific DNS cache entry'), which distinguishes it from the sibling 'seerr_flush_cache' likely targeting the entire cache. It also explicitly labels the operation as a WRITE, reinforcing the purpose.

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 use case is implied: use this tool when you need to clear a specific DNS cache entry. However, there is no explicit guidance on alternatives, prerequisites, or when not to use it. The description does not mention the sibling 'seerr_flush_cache' as the tool for flushing the entire cache.

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