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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuine behavioral substance beyond that: the membership rules differ between standard projects (every workspace member) and private ones (creator, owners/admins, explicitly added), and it enumerates the returned fields and role values. It does not mention pagination or permission requirements, which is the remaining gap.

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?

Front-loads the core action, then moves to return values, then to consumer linkage — a sensible information hierarchy with no filler. The middle sentence is long and clause-heavy, which costs a little readability.

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?

With no output schema, the description carries the burden of describing returns, and it does so fully (uid, full name, email, workspace role with enumerated values). For a single-parameter, read-only listing tool, nothing needed to call it correctly is missing.

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?

Only one parameter, project_id, and schema description coverage is 100%, so the schema fully documents it. The description implies the project scoping but adds no syntax, format, or constraint detail beyond the schema; baseline 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?

Opens with a specific verb+resource ('List the members of a project') and immediately differentiates itself from list_projects by scoping to project membership. It also distinguishes two sub-cases (standard vs. private projects) that an agent would otherwise have to infer.

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?

States the purpose-driven usage explicitly: resolve assignee uids 'instead of guessing names', and names the downstream consumers (create_card, update_card, create_epic, update_epic, create_roadmap_slot). No when-not or exclusion is given, but there is no real competing sibling, so the context is clear.

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