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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds only a light ownership scope ("the user's"), and says nothing about result size, ordering, or whether pagination applies — acceptable but thin given the annotations carry the burden.

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?

A single short sentence with the subject and scope front-loaded and no filler. It is efficient, though it borders on under-specification rather than tightness — one more clause on what is returned would have cost nothing.

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?

With no output schema and no parameters, the description is the only place an agent could learn what a returned project looks like or whether the entries carry identifiers usable with open_project. For a simple read tool this is close to adequate, but the missing link to the project-opening siblings leaves a real gap in a 70-tool surface.

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 and the schema is an empty object, so there is nothing for the description to compensate for. The baseline for a parameterless tool applies cleanly.

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?

States a specific verb (list) and resource (the user's projects), which is unambiguous on its own. However, it gives no signal distinguishing it from nearby siblings such as current_project, open_project, and account_status, so an agent must infer the relationship between listing, opening, and the active project.

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?

There is no when-to-use guidance at all — nothing says whether this is the first step before open_project, whether it lists all projects or only those recently accessed, or what to do if the result is empty. The only implicit cue is "the user's," which scopes the listing but does not route the agent among alternatives.

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