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

Annotations declare destructiveHint=true and idempotentHint=true, and the description earns credit by explaining what the destruction actually is (visitors' sessions are terminated) and what idempotence looks like in practice (a rule_id that is not one of this app's rules changes nothing and returns the same answer). It also adds the unusual operational fact that the call works while the machine is offline. No contradiction with annotations.

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 sentences, front-loaded with the action and its side effect, then provenance, then edge-case behavior. Slightly repetitive in restating the confirm-with-nerdit_list_app_access idea twice, but no filler.

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 destructive mutation with no output schema, the description covers side effects, no-op semantics, and offline operability, which is most of what an agent needs. It omits permission/auth requirements and what happens when the last access rule is removed, which are minor remaining gaps.

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 baseline is 3, but the description adds meaning not in the schema: rule_id must belong to this specific app, and a mismatched rule_id is a silent no-op rather than an error. It adds nothing new for node_id or service_name, which the schema already documents with provenance.

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 states a precise verb and resource – remove one access rule of this app – and adds the non-obvious consequence that visitors' sessions end simultaneously. It also names nerdit_list_app_access as the source of rule_id, which cleanly separates it from the sibling enumeration tool.

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?

It tells the agent where to obtain rule_id (nerdit_list_app_access) and how to verify a successful revoke. It never explicitly names nerdit_grant_app_access as the inverse operation or states when not to revoke, but the grant/revoke pairing is unambiguous from the tool names.

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