technitium_flush_cache

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

With no annotations, the description carries the full burden: it discloses that the flush is cache-wide and gated behind user confirmation, which are useful traits. However, it omits whether the action is reversible, its effect on in-flight/following queries, and any permission requirements for a state-changing 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?

Two short sentences with no filler, and the destructive action plus its gating instruction are both front-loaded. Every clause 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?

An output schema exists, so return values need not be described, and the single parameter is explained. For a destructive, annotation-free tool the description could say more about impact after flushing, but nothing needed to invoke it correctly is missing.

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%, so the schema alone leaves 'confirm' unexplained. The description compensates by defining both the workflow (ask the user) and the value to send (confirm=true), which is enough for an agent to set the single flag correctly.

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?

States a specific verb and resource ('Clear the whole DNS cache') with an explicit scope qualifier ('whole'), so an agent knows it is not a selective/per-zone purge. It does not differentiate from siblings, but none of the listed siblings is a competing cache-clear operation, so the differentiation gap is minor.

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?

'Ask the user first, then set confirm=true' gives a clear precondition for invocation. There is no need for when-not guidance or alternatives since no sibling performs an overlapping operation, so this is clear context without exclusions.

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