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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely non-structured context: the listing is account-wide and the result is a dependency for downstream calls. It does not mention ordering, pagination, or what an empty account returns, which keeps it short of 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?

Three short sentences, ~30 words, front-loaded with the action and followed by scope and then the sequencing rule. The last two sentences slightly overlap in meaning (the dependency and "Call this first"), which is a small redundancy rather than a real cost.

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 burden is light, and the description covers scope plus the prerequisite role that matters most for this tool. It stops short of describing the returned project fields, so an agent still learns the shape of the response only by calling it.

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 the schema baseline applies and no parameter explanation is required. The description correctly avoids inventing filter semantics that the empty input schema does not support, staying consistent with the contract.

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 ("List every project on the account") and immediately scopes it as account-wide, which distinguishes it from get_project (single project) and create_project. The follow-up sentence clarifies what a project is, so an agent knows what it is enumerating.

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?

Explicitly tells the agent when to call it: "every other tool needs a project_id from here. Call this first." That is a concrete ordering rule and a named prerequisite relationship, not an inference the agent has to make from sibling names.

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