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

The description discloses that the tool returns task counts, tier, status, and linked goal, which adds value beyond the annotations. Annotations already indicate read-only and non-destructive behavior. There is no contradiction. However, it doesn't mention default filtering behaviors like excluding archived projects, though that is covered in the schema. It doesn't cover pagination or sorting.

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 sentence with no unnecessary words. It states the action, resource, and key output fields efficiently. It is front-loaded with the primary action.

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?

The description is adequate for a simple list tool. It specifies the output fields and the action. It doesn't mention pagination or sorting, but given the schema covers filtering and default behaviors, it is reasonably complete. It could benefit from mentioning that it's read-only (though annotations cover that) or that it lists all projects by default.

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?

Schema description coverage is 100%, so all parameters (tier, status, include_archived) are documented with descriptions. The description text does not add any additional parameter semantics, so it provides no extra value beyond the schema. Baseline score of 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?

The description clearly states the action (List) and resource (projects), and specifies the fields returned (task counts, tier, status, linked goal). It is distinct from other list_* tools by focusing on projects, though it doesn't explicitly differentiate from get_project_analytics or other project-related tools.

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 no guidance on when to use this tool versus alternatives. It doesn't mention any exclusions or alternatives, such as using get_project_analytics for analytics or update_project for modifications. The usage is implied by the name but not explicitly stated.

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