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

Goes well beyond the annotations by disclosing the ~10 second propagation delay, the HTTP 403 failure mode, that IP and Origin rules are conjunctive, and that deactivation opens the node to any IP and origin. This is exactly the consequence information an agent needs before a destructiveHint=true call.

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?

Front-loaded with the one-line action sentence, followed by consequences in decreasing importance. Dense and mostly waste-free, though the IP/Origin explanation could be tightened slightly.

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?

Output schema and annotations are present and the description covers the destructive blast radius, timing, and failure behavior. For a 2-parameter toggle there is nothing an agent needs that 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 the baseline is 3, but the description adds real semantics: it explains what "activated" enforces and what "deactivated" opens up, not just the enum labels. node_id semantics are left to the schema, which already documents the ND- format.

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 pair and resource ("Activate or deactivate every access rule on a node at once") with explicit scope. The phrase "every access rule ... at once" cleanly separates it from the per-rule siblings create_node_access_rule / update_node_access_rule without needing to name them.

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?

Gives a concrete precondition before invoking: "First confirm with the user that the IP rules cover every IP that calls the node", plus a warning that origin rules block header-less clients. It does not explicitly route to the single-rule alternative for narrower changes, so it stops short of full when/when-not guidance.

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