set_blocking

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

Without annotations, the description must disclose behavioral traits. It mentions the auto-revert feature via timer, which is useful, but it does not disclose potential side effects of changing blocking state, permissions required, or behavior changes when timer is not set. This leaves gaps in understanding the full impact.

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 extremely concise: three lines including a clear purpose, parameter explanations, and an example. Every sentence adds value with no redundancy, and the most important information is front-loaded.

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 tool with two parameters and no output schema, the description covers purpose, parameters, and usage example. It is largely complete but could mention the return value or confirm that timer=null means permanent change. Still, it provides sufficient context for most use cases.

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?

The schema has 0% description coverage, so the description carries full burden. It clearly explains both parameters: enabled means 'True to enable, False to disable' and timer as 'optional seconds before blocking auto-reverts,' with a concrete example. This adds significant meaning beyond the schema types.

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 as 'Enable or disable DNS blocking,' using a specific verb and resource. It clearly distinguishes from sibling tools like get_blocking_status, which reads the status instead.

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 for changing blocking status but provides no explicit guidance on when to use this tool versus alternatives, such as when to prefer get_blocking_status for checking state. No exclusions or context for timer usage are given.

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