list_members

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

With no annotations, the description carries the disclosure burden. It explicitly mentions caching behavior (5 min) and the data returned, which are useful behavioral traits. However, it does not state whether the operation is read-only or if any authentication is required, though 'List' implies a safe read. The provided details add value beyond trivial behavior.

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 a single, front-loaded sentence that lists the action, key caching detail, and returned fields. Every phrase adds value and there is no redundancy or filler, making it highly concise and well-structured.

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, parameterless list tool with an output schema, the description covers the essential context: what it does, caching, and return fields. It does not mention pagination or authentication, but the tool's simplicity and the presence of an output schema reduce the need for additional detail. It is complete enough for an agent to use effectively.

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?

This tool has zero parameters, and schema coverage is 100% (vacuously). Per calibration, a tool with no params gets a baseline of 4. The description does not need to explain parameters since there are none, and it correctly focuses on output and behavior.

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 'List project members' with a specific verb and resource, and distinguishes it from sibling tools like list_labels and list_tasks by focusing on members. It also specifies the return fields (id, display_name, email), making the purpose 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 'cached 5 min' note gives an implied usage guideline about data freshness, but there are no explicit alternatives or when-to-use/when-not-to-use instructions. The description does not mention other tools for more current data or when this tool should be preferred.

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