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

Annotations already declare readOnlyHint=true, so the read-only safety profile is established. The description adds useful behavioral context beyond that: results are newest-first and the live deploy is marked. This helps an agent interpret output without contradicting the annotations.

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?

The description is a single, front-loaded sentence with no filler, repetition, or unnecessary explanation. Every phrase earns its place by conveying ordering and live-marking behavior.

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 simple two-parameter, read-only listing tool, the description covers the core operation, ordering, and a distinguishing output trait; the limit default is covered in the schema. It lacks explicit usage exclusions and an output schema, but an agent has enough information to invoke the tool correctly.

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 schema documents the limit parameter (default 20, max 100), but the required site parameter has no description. The description's phrase 'a site's recent deploys' gives minimal semantic context for site, but does not clarify the format or allowed values. It adds marginal value but does not fully compensate for the missing schema documentation.

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?

The description states a specific action ('Show'), a resource ('a site's recent deploys'), and adds ordering ('newest first') and a distinctive output trait ('marking the live one'). This clearly distinguishes it from sibling list tools like list_sites, list_files, and list_domains, and from rollback, which mutates deploys.

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 description makes the tool's purpose obvious, so when to use it is implied: whenever read-only deploy history for a site is needed. However, it does not explicitly state when not to use it or name alternatives such as rollback for changing the live deploy, so the guidance is not fully explicit.

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