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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered; the description adds ordering (newest first) and enumerates the returned fields (id, name, url, scenarioCount, lastRunStatus, lastRunAt, passRate), which compensates for the missing output schema. It does not mention pagination or result caps, a minor gap given annotations carry the rest.

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?

Front-loaded with the core scope and ordering, and nearly every clause carries information (domain definition, search semantics, returned fields, id handoff, check boundary). The final sentence packs the check relationship and projectId alias densely, costing a bit of readability, but nothing is wasted.

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 one-optional-param read tool with no output schema, the description supplies both the returned field list and the cross-tool id usage, so an agent has everything needed to call it and consume the result. No meaningful gaps remain.

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?

Schema description coverage is 100% and the schema already documents the search parameter as a case-insensitive substring over name or URL with a 200-character cap. The description's 'Optional search matches the name or URL, case-insensitive, up to 200 characters' is a near-verbatim restatement rather than added meaning, so baseline 3 applies.

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 owned by the authenticated account'), defines scope, ordering ('newest first'), and even defines the domain object ('A project is one web app'). The agent can distinguish this from siblings like list_scenarios or check without opening any 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?

Explicitly routes the returned id to list_scenarios, run_project, or check as projectId, and clarifies the boundary with check ('check creates a project when no owned environment matches the URL'). Both the when-to-use and the alternative-tool conditions are spelled out rather than implied.

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