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

Beyond the readOnlyHint annotation, the description discloses meaningful behavioral traits: it is credential-scoped ('only the projects the calling credential may see'), it takes no arguments, its results are mandatory for subsequent calls, and it explicitly excludes components, packages, and tokens. This materially helps the agent predict side effects and prerequisites.

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 four sentences, each earning its place: output content, read-only and scoping, usage ordering, and explicit exclusions with alternative tools. It is front-loaded and dense without extraneous detail.

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-parameter read-only tool, this description covers what an agent needs: return shape, auth scoping, why it must be called first, and what it is not responsible for. No critical operational context is missing.

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 input schema is empty, so there are no parameter semantics to clarify; the 0-parameter baseline of 4 applies. The description still confirms 'takes no arguments,' matching the schema without contradiction.

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 opens with a specific verb plus resource ('Lists the projects in this organization') and states exactly what fields are returned (id, name, framework). It explicitly contrasts with sibling tools like list_components, list_packages, and get_style_tokens, making the tool's scope unmistakable.

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 description gives explicit usage guidance: 'Call it first in a session' and explains that the returned id is the project_id required by every other tool and that guessing it fails. It also names alternatives for components, packages, and tokens, so when-not-to-use is crystal clear.

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