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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description's help. The description adds only the filter vocabulary and says nothing about result size, auto-pagination across pages, or the fact that omitting filters returns everything.

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?

Two short sentences, no filler, with the core verb-resource statement front-loaded and the filter list second. It is efficient, though the second sentence is largely a restatement of parameter names and could carry more load.

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 read-only list tool with no output schema, the definition is serviceable but thin: it omits the pagination/auto-fetch behavior and expected result shape that an agent calling a 6-parameter list endpoint would benefit from. Annotations cover safety, so nothing critical is missing, but the description under-delivers on operational context.

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% with all six parameters documented (including pagination defaults and the Clerk ID meaning of user_id), so the schema carries the semantics. The description echoes three of those filters (project, user, active status) without adding syntax or format detail, which is the expected baseline 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?

States a specific verb plus resource ('List project team members') and enumerates the filter axes, which is clear on its own. It does not, however, distinguish itself from the close siblings get_project_team_member (singular) or list_users, so an agent must infer the scope difference from naming alone.

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 names the filters but gives no when-to-use guidance, prerequisites, or alternatives. Nothing tells the agent when to prefer this over get_project_team_member, list_users, or list_projects, so selection rests entirely on the tool name.

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