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

Annotations already cover the read-only, non-destructive, idempotent nature of the operation. The description adds valuable behavioral context beyond those annotations, including the auth requirement, the plan limitation, and the fact that entries represent pending approval rather than full allowlist membership.

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 with no filler: the first states the core purpose, the second summarizes the return fields, and the third covers auth, plan limitation, and the relevant sibling tools. Every sentence earns its place.

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 read-only list tool, the description is complete: it explains what is listed, what each entry contains, who may call it, and what plan requirement applies. The absence of an output schema is partially mitigated by the explicit field list, and no pagination or sorting details are strictly necessary for a correct call.

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%, so the schema already fully documents both site_id and workspace_id. The description doesn't add parameter-specific detail beyond defining the resource scope ('for an allowlist site'), which is fine given the schema carries the burden.

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 and resource: 'List pending access requests for an allowlist site', and clarifies exactly what these are ('people who asked to view it and are waiting for approval'). It goes on to name the approve/reject sibling tools, which makes its purpose unambiguous against the large sibling list.

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 clear context for when this tool applies: pending requests awaiting approval, with explicit prerequisites ('Admin or owner only; requires a plan with access requests enabled'). It names approve_access_request and deny_access_request as follow-up actions, though it does not explicitly contrast this with list_allowlist for already-approved members.

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