technitium_blocking

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

With no annotations, the description carries the burden. It discloses the important behavioral traits that this is a state-mutating operation and that confirm must be set after user consent, which is genuinely useful. It omits reversibility, interaction/precedence between minutes and enable, and any auth/permission requirements.

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?

Four short lines, front-loaded with the overall action, then one line per parameter, ending with the confirm rule. No filler. The terseness borders on leaving gaps, but 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?

An output schema exists so return values need not be explained, and the param meanings are present. Still missing for a mutation tool with zero annotations: what the two modes do when combined, whether changes take effect immediately, and any scope/permission caveats.

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 0%, so the description must supply all param meaning. It does cover all three: minutes (pause duration), enable (permanent switch), and confirm (set true after asking the user). It adds no types/defaults/ranges, but the semantic intent of each parameter is clear.

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 (turn on/off/pause) and a specific resource (ad blocking), with the three operating modes spelled out (temporary pause, permanent enable, permanent disable). It does not explicitly differentiate itself from siblings like technitium_settings_set, but the resource is 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 usage through the mode breakdown and adds a real workflow rule, 'Ask the user first, then set confirm=true.' However, it never states when to prefer this over sibling tools like technitium_settings_set, nor what happens if minutes and enable are supplied together.

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