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

Beyond the annotations, the description discloses important behavioral details: the recipient can reply with approve/reject or quote the message, an approvalId is returned, and the outcome can be retrieved via polling or webhook. It also mentions the authentication requirement ('nrn_' prefix API key). These add value beyond the readOnlyHint/idempotentHint/destructiveHint flags without contradicting them.

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?

The description is three well-structured sentences that front-load the core purpose, then cover usage context, return value, follow-up mechanisms, and authentication. No sentence is redundant, and it remains readable despite the tool's complexity.

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?

Given the tool's complexity (9 parameters, nested callback object, no output schema), the description provides sufficient context about the request flow, return value, and how to obtain the decision. It leverages the rich schema descriptions for parameter details and adds enough guidance for an agent to invoke the tool effectively, though a brief note on response structure would make it fully complete.

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 100%, and each parameter already has a detailed description. The tool description adds some high-level context around `callback` and the API key but does not significantly enhance the per-parameter semantics, so the baseline score of 3 is appropriate.

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 clearly states the tool's purpose: asking a human to approve or reject an action over WhatsApp and returning the decision. It uses a specific verb-resource pair and distinguishes itself from related sibling tools like neuron_respond_approval, neuron_get_approval, and neuron_cancel_approval by focusing on the initiation of the approval request.

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 explicitly says 'Use this to gate any action needing human sign-off' and provides concrete examples (refunds, deploys, spend, publishing). It also offers clear alternatives for receiving the outcome, such as polling neuron_get_approval / neuron_list_approvals or supplying a webhook callback, though it does not explicitly state when not to use this tool.

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