list_team_members

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

No annotations are provided, so the description must fully convey behavioral traits. It mentions pagination but does not disclose other behaviors like result ordering, total count availability, or any side effects. The tool is a list operation, but its safety and limitations are not elaborated.

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 very concise at two sentences, front-loading the core purpose. It could include slightly more information without being wasteful, but it efficiently conveys the essential operation.

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?

The tool has 4 parameters and no output schema. The description lacks critical context such as response structure, default ordering, filtering capabilities, and any prerequisites. For a list endpoint with sibling tools, more completeness is needed to guide proper use.

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 coverage is 100% with detailed parameter descriptions. The description adds 'Supports pagination', which corresponds to page and per_page parameters, but provides no new semantic meaning beyond the schema. Baseline score of 3 is appropriate.

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 members of a team' which clearly identifies the verb ('list') and resource ('members of a team'). It distinguishes from sibling tools like 'add_team_member' and 'remove_team_member' by focusing on listing only.

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?

No guidance on when to use this tool versus alternatives, such as filtering or context like limited team membership retrieval. The description only mentions pagination support, which is implicit in the page parameters.

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