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

Annotations already cover the safety profile (readOnlyHint true, destructiveHint false), and the description adds real context beyond them: results are ordered newest first, entries include status, and the call is non-interactive ('asks no human'). It omits pagination behavior, which matters given cursor/limit, keeping 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?

Two tight, front-loaded sentences with no padding. The second sentence is slightly cryptic in phrasing but still adds information an agent can act on.

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 read-only list tool with no output schema, the description conveys ordering and per-item content, but leaves pagination (limit/cursor) and the full record shape unexplained, which an agent needs to call it reliably.

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 coverage is only 50% – project and environment are documented, but limit and cursor carry no description anywhere. The description does not compensate, saying nothing about page size caps or cursor continuation despite 'newest first' implying a paged order.

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?

Names the resource (an Environment's Deployments) and the ordering (newest first) plus what each entry carries (status), which distinguishes it from deployment_show by implication. However, it never states an explicit verb like 'list' and never names deployment_show as the single-record alternative.

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?

'This call asks no human' is a hint that it will not block on approval, but there is no explicit when-to-use or when-not, and no routing vs deployment_show or the mutating siblings (deploy, deployment_start, deployment_cancel).

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