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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so 'Read-only' in the description is largely redundant. Beyond that, the description adds the returned fields and the chaining hint, which is useful, but says nothing about result volume, pagination, or scope limits for organizations with many projects.

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 short sentences, front-loaded with what is listed and what each record contains. Nothing is repeated needlessly and no sentence is 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 zero-parameter, no-output-schema list tool, the description covers purpose, returned fields and next step. The only real gap is unspecified pagination or result-size behavior, which matters if the organization has many projects.

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 is 4. The description correctly implies no filtering arguments are available and instead explains how to use the returned ids downstream.

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 (lists Search projects) and enumerates the fields returned (id, name, item count, trial status). It distinguishes itself from search_project by pointing to that tool, though it doesn't explicitly contrast with the similarly named search_create_project sibling.

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 a project id from here with search_project" gives an explicit follow-up action, which is the main routing decision for this tool. It doesn't state exclusions (e.g., when to call search_public_catalogue instead), so it falls short of a full 5.

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