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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false. The description adds the real operational consequence that annotations cannot convey: turning it off makes the site begin actively blocking traffic, while on runs all checks in observation mode. That is material context for a state-changing toggle, though permissions or reversibility are not stated.

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?

Three short sentences, front-loaded with the action and then the two state meanings. Every sentence carries information; 'nobody is turned away' is the only phrase that leans colloquial but still conveys that traffic passes through.

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 two-parameter boolean toggle with full schema coverage, complete annotations, and an output schema that covers return values, the description supplies everything needed to invoke it correctly. Nothing an agent must know before calling 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 coverage is 100%, so both parameters are already documented, setting the baseline at 3. The description elaborates watch_only's two states ('every check runs and shows what would be blocked' / 'starts blocking'), which slightly exceeds the schema text but largely restates it.

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+resource: toggling 'watch only' on or off for a BurrowGuard site. An agent can distinguish it from create_burrowguard_site and list_burrowguard_sites by the action, though no sibling is named explicitly.

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 what each mode means, which implies when you'd flip it, but it never states preconditions (site must already exist), nor when to prefer this over creating a new site or checking results via list_burrowguard_checks. Usage is implied rather than directed.

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