list_project_members

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

With readOnlyHint=true already declaring safety, the description adds that results are scoped to the 'current project' and that the IDs are meant to feed assigned_to, which is useful context. However, it never explains how the 'current project' is determined given there are zero parameters, which is the one real behavioural question an agent would have.

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?

A single compact sentence that front-loads the action and closes with the practical payoff, the assigned_to-ready account IDs. Nothing is redundant or padded.

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 parameterless read with an output schema already documenting return values, the description covers purpose, scope, and intended downstream use. The only gap is the unresolved question of how 'current project' is established, which is a minor omission at this complexity level.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate beyond what the empty schema shows. The baseline of 4 applies; the description implicitly confirms the no-argument nature by describing project scope as 'current' rather than parameterized.

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 gives a specific verb+resource (list current project members) plus what is returned (members and their roles). It stops short of naming how it differs from siblings like get_current_user, but no sibling competes for the same listing job, so the purpose is unambiguous.

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 clause 'returns account IDs usable for assigned_to' tells the agent the exact situation that calls for this tool — resolving a user identifier before create_workitem or update_workitem. It gives no explicit exclusions or alternative sources, but the positive context is clear.

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