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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is fully covered structurally. The description adds the notion of a login gate and host attestation flags, which hints at per-project state, but says nothing about ordering, pagination, or whether all projects or only accessible ones are returned.

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?

Two sentences, zero waste: the first front-loads what is listed and its fields, the second gives the chaining instruction. Nothing is repeated or padded.

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 inputs, an output schema, and rich annotations, the only things an agent needs are purpose and how to use the result, both of which are present. Minor gap: it never mentions ordering or behaviour if the project list is large.

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 for the description to disambiguate. Baseline 4 applies; the field enumeration adds a little context but no parameter semantics exist to document.

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 the organisation's projects') and then enumerates the exact fields returned (id, name, target URL, login gate, guides, attestation). This clearly separates it from siblings like list_runs, list_voices, and create_project without needing to open a schema.

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?

'Use the id with the other tools' explicitly tells the agent how this tool feeds downstream calls, which is the key workflow context for a discovery/list tool. It stops short of stating when to prefer this over get_credits, list_runs, or update_project, but the resource distinction makes the alternatives obvious.

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