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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds genuinely new behavior: results are newest-first, the record includes status/failure message/bundle version/deployer/time, and notably that a failed deployment leaves the previously-ready bundle running. That last point is real operational context an agent could not infer.

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 sentences, front-loaded with what the tool returns and what it is for. No filler, no redundancy.

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 output schema, the description usefully enumerates returned fields and ordering, which is the right instinct. However, the three input parameters are entirely undocumented at 0% schema coverage, so an agent cannot tell what limit does or how status filtering behaves.

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 0%, so the description must carry the burden, and it largely does not. 'For a project' hints at project_id, but limit and the status enum (pending/deploying/ready/failed) are never explained, and the fields listed (bundle version, deployer) are return values, not parameters.

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 ('Deployment history for a project'), plus ordering ('newest first') and the fields returned. It implicitly contrasts with the sibling deploy_functions via the 'did my deploy work' framing, but never names an alternative explicitly, so it falls short of full sibling differentiation.

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?

The phrase 'did my deploy work' implies the post-deploy verification context, which is useful, but there is no explicit when-to-use guidance, no conditions, and no named alternative (e.g. deploy_functions for triggering a deploy vs. this for checking one). Usage is left to inference.

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