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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds real value beyond them: the result set is limited to projects visible to the current user, and it imposes a strict output-handling rule that link_url must be reproduced verbatim and never rebuilt. Missing are any notes on result size or ordering, which is why this is not a 5.

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 definition is front-loaded with the core purpose, then follow-up usage, then the link-fidelity warning. The bolded Links block is longer than the rest of the description combined, but it encodes a non-obvious formatting constraint that would otherwise cause silent errors. Slight trimming of the emphasis markup would make it tighter without losing content.

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 input parameters and an output schema present, the description does not need to explain return values, and it correctly focuses on purpose, visibility scope, and next-step tooling. The only gap is operational detail such as ordering or volume of results, which is minor for a zero-argument list tool.

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 there is nothing to disambiguate and the baseline is 4. The mentions of 'id' and 'link_url' refer to returned fields, not inputs, and do not create confusion about how to call the tool.

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 uses a specific verb and resource ("Returns all projects") and scopes them with "visible to the current user", which separates it from the content/blueprint/plan list tools. It also briefly defines what a project is ("organize content into workstreams"). It stops short of explicitly contrasting itself with other list_* siblings, so it is clear rather than exemplary.

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?

It gives concrete downstream guidance: use the returned 'id' with get_project for details, or pass project_id when creating content. That tells an agent how this tool fits into a workflow. It does not state when not to call it or name an alternative listing path, so it is clear context rather than full when/when-not guidance.

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