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

Annotations already declare the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), lowering the bar. The description adds two useful pieces of context beyond annotations: the required OAuth scope ('mcp:read') and the scoping that only projects accessible to the current connection are returned. However, it offers no further behavioral details such as pagination limits or response shape, making it adequate but not rich.

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 very short and front-loads the core resource information, with the auth requirement in a parenthetical. There is no wasted text. The only minor issue is that it is a sentence fragment rather than a fully formed sentence, but it remains clear and appropriately sized for a zero-parameter tool.

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 low complexity (no parameters, no output schema, simple read), the description covers the essential purpose and authorization requirement. However, it does not mention whether the result is paginated, how many projects might be returned, or in what format, leaving gaps that could affect an agent's expectation. It is adequate but not fully complete for a 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 takes zero parameters, so the baseline score is 4 per the rubric. With no parameters, there is no parameter semantics to describe, and the schema is effectively trivial. The description does not need to add parameter details, so this is appropriately scored.

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 the resource ('The projects') and a scoping constraint ('this connection may use'), but lacks an explicit action verb like 'list' or 'returns'. It is not a tautology because it adds the connection-scope qualifier, but it remains a vague purpose statement rather than a clear verb+resource definition. It also does not distinguish itself from the similarly named sibling 'list_sessions'.

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?

No guidance on when to use this tool versus alternatives is provided. The only contextual note is a prerequisite ('Requires scope mcp:read'), which is an authorization requirement rather than usage direction. There is no mention of when-not-to-use or any alternative tool.

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