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 the tool may create a project if it doesn't exist (a side effect) and what the brief contains, but says nothing about permissions, idempotency, or what creation does with name/description.

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?

Three dense sentences, front-loaded with the primary action and return content before the listing mode and slug syntax. Nothing is wasted, though the slug-format detail could be folded in more tightly.

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?

An output schema exists, so return values need not be re-explained, and the listing mode is covered. However, for a tool that can create, the roles of `name` versus `project` and `description` remain unresolved, leaving an agent guessing how to initialize a new project.

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 0% — the schema only exposes bare titles (Name, Project, Description). The description compensates for `project` by giving the slug format and omission semantics, but leaves `name` and `description` entirely unexplained, likely the creation fields.

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 and resource ('Open (or create) a project') and enumerates the returned brief (status line, open tasks, decisions, failed attempts), which is far more than a restated title. It does not explicitly name siblings like project_status, so differentiation is left to inference.

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?

'Call this first in a session' gives a clear entry-point condition, and 'Omit `project` to list your projects' describes the alternate mode of use. No sibling alternatives (project_status, recall) are named or contrasted, so it stops short of 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.