dns_flush_blocked

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

No annotations are provided, so the description must convey all behavioral traits. It discloses the destructive action (removing all manually blocked domains) and the confirm parameter, but does not mention permissions, reversibility, or effects on other blocked entries from blocklists. Adequate but not comprehensive.

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?

Two sentences with no wasted words. The first sentence immediately states the action, and the second clarifies the confirmation requirement. Front-loaded and efficient.

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 the simple single-parameter tool and the absence of an output schema, the description adequately covers the essential aspects: action, effect, and prerequisite. It could mention the impact on non-manual block entries, but the tool is sufficiently described for its purpose.

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% with one parameter (confirm). The description adds value beyond the schema by explaining that confirm=true is required for execution and that omitting it returns a warning.

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 explicitly states the tool flushes the entire custom block list and removes all manually blocked domains, clearly distinguishing it from sibling tools like dns_remove_blocked which targets individual domains.

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 explains the confirm parameter requirement but does not provide explicit when-to-use or when-not-to-use guidance. It implies usage for bulk removal but lacks comparison with alternatives like dns_remove_blocked or dns_temp_disable_blocking.

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