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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds authentication requirement ('Requires a bot API key') and organization scope, but no additional behavioral details like pagination behavior or response shape.

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 sentences, front-loaded with the core action. Every phrase adds value: scope, ordering, filter options, and authentication requirement. No wasted words.

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 filtered list tool with comprehensive annotations and full schema coverage, the description covers purpose, ordering, filters, and authentication. No output schema exists, but this is adequate for a simple list operation, and the description is complete for the task.

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%; all five parameters (apiKey, page, limit, status, channelId) have descriptions. The description mentions status filter and apiKey requirement but does not add significant meaning beyond the schema, except for the 'organization' scope.

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 'List approval requests for the organization, newest first' with a specific verb (list), clear resource (approval requests), and ordering (newest first). This distinguishes it from sibling tools like neuron_get_approval (single approval) and approval action tools.

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?

Provides clear usage context: organization scope, newest first, and specific status filters. It does not explicitly name alternatives or state when not to use this tool, but the listing context is clear.

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