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

The annotations already declare this as read-only, idempotent, non-destructive, and closed-world. The description adds meaningful authorization behavior by stating that projects outside the connector's grants never appear, plus it enumerates returned fields. It does not explain pagination behavior despite exposing result_offset, so it is strong but not complete.

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 two sentences, front-loaded with the core operation and usage trigger, followed by return fields and access scope. Every sentence adds useful information without filler.

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 list tool with no output schema, the description names the returned fields and explains authorization filtering, which is enough for an agent to understand what it gets back. The main gap is the unexplained result_offset parameter and missing pagination semantics.

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?

There is one optional parameter, result_offset, and the schema has 0% description coverage. The description never mentions offset, pagination, or ordering, so it adds no meaning beyond the parameter name and type.

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 gives a specific verb and resource ('List the projects') and scopes it to projects the connector is authorized to read. It clearly distinguishes this discovery operation from sibling tools like read_project by framing it as the first step when no project_id is known.

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 explicitly says to use this as the first step when no project_id is known, which is clear when-to-use guidance. It does not explicitly name read_project as the alternative once an id is known, so it falls just short of fully explicit alternative routing.

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