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

With no annotations, the description carries the full burden. It usefully discloses that results are scoped to the authenticated user and that the tool returns "all" projects, which implies no filtering or pagination input, but it says nothing about ordering, archived-project handling, or the shape of the returned records.

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?

One short sentence with the scope qualifier placed immediately after the action. No filler and nothing to trim.

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 zero-argument, read-only listing tool this is close to adequate, but with no annotations and no output schema the description should say something about what a project record contains and whether the list is paginated or bounded, which it does not.

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 schema has zero parameters, so there is nothing for the description to clarify; the baseline for a no-parameter tool applies. The mention of the authenticated-user scope is a small extra, but the tool takes no inputs to describe.

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 (projects) plus a scope qualifier (for the authenticated user). Among siblings that include createProject and many other list* tools for different resources, the resource name alone is enough to disambiguate, though no sibling is named explicitly.

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 intent is implied: use this to enumerate the caller's projects. There is no explicit statement of when to prefer it over alternatives such as getClientView, nor any exclusion (e.g. whether archived or shared projects are included).

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