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

No annotations are provided, so the description must carry the full burden. It states that the operation is read-only in effect ('List') and implies no side effects, which is important behavior. It also adds the token-scoping constraint, indicating it operates within the token's permissions. However, it doesn't detail output format or pagination, which could be relevant, but for a simple list operation the core behavior is clear.

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, concise sentence with no wasted words. It front-loads the verb and resource, and clearly communicates the tool's purpose and scope without 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?

Given the tool's simplicity (zero parameters, no output schema), the description is complete enough for an agent to call it correctly. It clearly states what it does and the scope. Minor gaps, such as details about the return format or pagination, are not critical for a simple list operation.

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 has zero parameters, and the schema is empty. The description doesn't need to explain any parameters. The score of 4 aligns with the baseline for zero parameters, as no compensation is required.

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 specific verb ('List') and resource ('projects') and clarifies the scope ('accessible with this token'). It is clear and distinguishes from sibling tools like create_project or get_project. However, it doesn't explicitly contrast with the sibling get_project, which also deals with projects, though 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 description implies usage: use this to list projects, but it does not explicitly state when to use it versus alternatives. It doesn't mention when not to use it or point to siblings like get_project for a single project. There's no guidance on scenarios like filtering or pagination.

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