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

Annotations already cover the safety profile (idempotentHint=true, destructiveHint=false, openWorldHint=true). The description adds real behavioral value beyond them: approved people become named viewers, optionally bounded by expiresAt, gain access on their next visit without a new link, and are notified either way. It does not, however, disclose permission/auth requirements.

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?

Two tight sentences, front-loaded with the core action and then the consequences. Every clause earns its place with 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 mutation tool with no output schema, the description covers the key effects (viewer status, expiration, notification) well. It omits error cases and required permissions, but is otherwise suitable for correct invocation.

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 description coverage is only 25%, with just expiresAt documented. The description adds meaning for expiresAt ('optionally until expiresAt') and reinforces the decision enum, but leaves siteId and requestId unexplained. Partial compensation for a low-coverage schema, landing at baseline.

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 specific verb pair and resource: 'Approve or deny an access request,' which is clear and actionable. However, it does not differentiate from similarly-named siblings like neuron_handle_join_requests or neuron_respond_approval, so an agent must rely on the tool name for scoping.

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 offers no when-to-use guidance, no prerequisites, and no mention of alternatives among the many approval/request siblings. It implies the action ('approve or deny') but never tells the agent when this tool is the right choice.

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