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

Annotations already establish this as a safe, read-only, idempotent operation, so the bar is lower. The description adds useful behavioral context: it discloses the fields returned, that results are ordered newest first, and that banned or churned members are included. It does not mention pagination or rate limits, but the schema covers pagination parameters.

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 a single, front-loaded sentence with zero waste. Every phrase—returned fields, ordering, and status inclusion—provides useful information. It is appropriately sized for a list tool with a fully documented schema.

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 presence of annotations covering safety and a fully described schema, the description is adequate but not complete. It explains the return shape and ordering well, but lacks guidance on when to use this tool instead of search_members or get_member. Adding that usage context would make it more 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%, so all six parameters are fully documented in the schema itself. The description does not add any meaning beyond what the schema provides for parameters like role, status, or joined_since. Baseline 3 is appropriate when the schema does the heavy lifting.

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 identifies the resource (members of a group) and lists the specific fields returned (role, level, points, join date), along with ordering. It distinguishes the tool from a single-member lookup by implying a list, but does not explicitly differentiate it from siblings like search_members or get_member.

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 implied by mentioning that it returns members including banned or churned ones, suggesting it's for browsing member lists. However, it does not specify when to use this tool versus search_members or get_member, nor does it give explicit when-not conditions.

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