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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It reveals key behavior: only owner and accepted members are returned, email is used as a fallback when a member lacks a name, and project selection prefers a workspace config over the API key default. It does not cover error cases or read-only guarantees, but 'List' implies a safe 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?

The description is concise and front-loaded: the core purpose appears first, followed by disambiguation guidance and project-selection behavior. Every sentence adds necessary information with no filler or repetition.

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 simple one-parameter list tool with no output schema and no annotations, the description is largely complete. It names the returned fields, explains the fallback email behavior, and clarifies project selection. It could be slightly more explicit about what happens when no projectName is available, but the API-key default is already implied.

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 input schema only defines projectName as a string with 0% description coverage, so the description must compensate. It explains how projectName is selected and that the API key's default project is the fallback, which gives real meaning to the parameter 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 clearly states a specific action ('List the people who can be assigned work in a project') and specifies the exact scope: the owner and accepted members, with names, roles, and ids. This is easily distinguishable from sibling list tools like list_projects and list_tasks, which cover different resource types.

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 provides actionable guidance: use the id to disambiguate when names collide, and prefer a workspace config's projectName when present. It does not explicitly name alternative tools or state when not to use this tool, but the intended context (assigning work, selecting a project) is clear.

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