list_team_members

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

Description aligns with readOnlyHint annotation, stating 'Retrieve'. Adds context about pagination and filtering but does not disclose other behaviors like rate limits, order, or error handling. Adequate given simple read operation.

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?

Description is concise with a single sentence and relevant examples, front-loading purpose. No unnecessary words.

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 list tool with output schema, the description covers pagination and filtering. Could mention default per_page value, but overall sufficient. Output schema fills gaps.

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?

Despite 0% schema description coverage per context signals, the description provides examples that demonstrate parameter usage. The examples help clarify team and cursor parameters, though per_page default is not mentioned. Partial compensation.

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 name and description clearly indicate the tool retrieves paginated team members with optional team filtering, distinguishing it from sibling tools like list_teams which list teams, not members.

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?

Examples show when to use the tool: default all members, filter by team, paginate. Usage is implied, but no explicit guidance on when not to use or alternatives. Clear enough for most cases.

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