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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds value by disclosing an access requirement ('administrative access') and clarifying that credentials and login links are excluded from the output, which is behavioral information beyond what annotations provide.

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 two concise sentences, with the primary action front-loaded. Every phrase adds value: the verb and resource, the output scope, exclusions, and access requirement. There is no fluff or redundancy.

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 read-only listing tool with one optional parameter, an output schema, and annotations covering safety, the description is sufficient. It covers the key aspects: what is returned, what is excluded, and access requirements. Pagination or filtering details are not mentioned, but the output schema likely handles return format, so this is not a critical gap.

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 schema covers the single optional parameter project_id with a full description, and the description adds no additional semantic meaning about the parameter. Since schema coverage is 100%, the baseline of 3 applies; the description does not compensate or extend parameter understanding.

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 states a clear verb and resource: 'List team members and project assignment'. It also specifies exclusions ('excluding credentials and login links'), which distinguishes it from other member-related operations like add_team_member or remove_team_member. The purpose is unambiguous and specific.

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 mentions a prerequisite ('Requires administrative access') but does not explicitly explain when to use this tool versus alternatives like list_projects or list_tasks. The usage context is implied by the resource name and verb, but no direct guidance is given about when to choose this tool over others.

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