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

Annotations already declare mutation (readOnlyHint=false, destructiveHint=false), and the description adds non-obvious side effects beyond them: every change logs viewers out within ~15 seconds, rotating the link kills the old link instantly, and password changes log everyone out. These are genuinely useful behavioral disclosures not present in the structured fields.

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?

Dense but front-loaded, leading with the core purpose before the option catalog. It reads as a run-on packed with inline clauses rather than a scannable list, but each clause carries distinct parameter meaning so little is wasted.

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 13-param mutation tool with no output schema, the description covers the access model, per-mode semantics, and key side effects well. It omits permission requirements and partial-failure behavior, but an agent has enough to invoke it correctly.

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?

With 54% schema coverage, the description meaningfully compensates: it decodes each generalAccess value ('restricted', 'link', 'request', 'org', 'domain', 'public'), notes that 'public' requires confirmPublic and 'domain' depends on allowedDomains, and explains that password applies to everyone but owners. A few params (allowReshare, requirePassword, peopleExpireAt) are left to the schema.

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 and resource ('Control who can open a site') with a clear mental model ('Google Docs style'). The scope is unambiguous and naturally distinct from sibling site tools like neuron_sites_respond_access_request and neuron_sites_get_access_requests.

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 gives rich context for each access mode and what each optional action does, which implicitly tells the agent when to use them. However, it never names or contrasts against sibling tools (e.g. respond_access_request) or states prerequisites/exclusions, so it falls short of explicit when/when-not routing.

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