get_project_members

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

Annotations indicate readOnlyHint=true (read-only). The description adds detailed behavioral context beyond annotations: filterable, paginated, case-insensitive contains for string filters, exact match for role_slug, and pagination envelope in returns. No contradictions.

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 well-structured: a one-line summary, optional filters grouping, and an Args section with each parameter's role. It is concise, front-loaded, and every sentence adds value.

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 moderate complexity (filtering, pagination), the description covers input, filters, pagination mechanics, and output format (paginated envelope with members, total_count, next_cursor, next_page_results). No 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 the context signal indicating 0% schema coverage, the description explicitly lists all parameters with their behavior (e.g., 'case-insensitive contains', 'omit for first page', '1-1000, default 100', sort prefix '-'). Adds significant meaning beyond the bare schema.

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 starts with 'List members of a project (filterable, paginated)', clearly stating the action, resource, and capabilities. It distinguishes from sibling tools like 'get_workspace_members' which lists workspace-level 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?

The description explains the use of optional filters with AND logic and cursor-based pagination. It implicitly guides when to use (to list project members), but lacks explicit when-not guidance or direct comparison to similar tools like get_workspace_members.

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