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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses binary files are listed but not returned, that republishing a release's files rolls back, that the git URL expires in an hour and cannot push, that it must not be shared or logged, that git cannot be combined with path, and that a Valet account is required. This is unusually rich behavioral context.

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 core behavior (list files vs read one file) is front-loaded before the release, rollback, binary, and git notes. It is dense with useful constraints rather than filler, though ten sentences is on the long side and the git guidance could be tightened.

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 carries the return-value burden and does so: it states that without path it lists files, with path it returns one file's text, binary files are withheld, and git returns a URL plus clone commands. An agent has everything needed to call it 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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: release controls reading an earlier release and carries rollback semantics, path switches between listing and fetching, and git's expiry and path-exclusion constraint are restated in prose. org_name is left entirely to the schema, which keeps this from a 5.

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 opening sentence states a concrete verb and resource: reading the published files of a website, app, agent, or skill's active release, with the list-vs-single-file distinction spelled out. This clearly separates it from sibling read tools like get_build or list_releases and from the publish_* family.

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?

It explicitly says when to use it ('Read before you change something someone else built, so your publish carries their work forward') and when to use the alternative ('Pass git: true instead... Prefer it to reading files one at a time'). It also names list_releases as the source of the release value, so routing is unambiguous.

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