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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered and the description only adds the org-scoping detail. However, 'List all customers' is slightly misleading because the tool paginates (default 30, max 100 per page), so a single call does not return all customers; the description never mentions this.

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?

A single, front-loaded sentence with no filler or redundancy. It is efficient, though its brevity is part of why pagination behavior goes unmentioned.

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?

This is a low-complexity, zero-required-parameter list tool with full schema coverage and an output schema, so return values need no explanation. The only meaningful gap is the implicit pagination versus the word 'all', which an agent would learn from the schema anyway.

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 every parameter (page, per_page, sort) is documented with defaults, bounds, and enum meanings directly in the schema. The description adds nothing about parameters, so the baseline of 3 applies.

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 uses a specific verb and resource ('List all customers') and narrows scope to 'in the organization', so an agent knows it is a tenant-scoped enumeration rather than a single-record fetch like get_team_member. It does not explicitly distinguish itself from other list_* siblings, but the resource noun is unambiguous enough that no confusion is likely.

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?

Usage is only implied: the agent can infer 'call this when you need a list of customers'. There is no explicit when-to-use framing, no statement that no filtering/search variant exists, and no guidance on when to page through results versus stopping.

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