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

The description repeats the read-only/side-effect-free behavior that is already fully declared by the annotations (readOnlyHint=true, idempotentHint=true, destructiveHint=false). It adds no additional behavioral context such as pagination, response size limits, or account scoping details beyond what annotations already provide.

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 two short sentences, front-loads the core action and resource, and includes a clear side-effects note. Every word 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 zero-parameter, read-only list tool with a rich output schema and full annotation coverage, the description is complete enough for an agent to select and invoke it correctly. No additional context is necessary.

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?

The tool has zero parametersasi and the schema covers 100% of what is needed (an empty object). The description doesn't need to explain parameters, so the baseline of 4 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 clearly states the action ('List') and the resource ('all corporate members in your account'). It is specific enough to distinguish from other list tools like list-contacts or list-faxes, but it does not explicitly differentiate from get-member-details, which is a close sibling for member-related operations.

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 implies when to use the tool: whenever the agent needs the full set of corporate members in the account. However, it provides no explicit guidance about when not to use it or which sibling tool might be better for individual member details or member management.

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