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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and locality are covered by structured data. The description adds useful non-schema context about what the result contains — new, regressed and resolved issues plus the version's deploy marker — but says nothing about pagination, limits, or error behavior when a version/appId pair doesn't match.

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?

A single dense sentence with no filler, and the primary resource ('One release') is front-loaded. The nested commas in 'by id or, with appId, by version' cost a little 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?

With no output schema, the description compensates by enumerating the returned payload (issue classifications and the deploy marker). For a two-parameter read tool with full schema coverage, that is close to complete, though a note on lookup failure or response shape would close the remaining gap.

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%, so the appId and releaseId semantics ('app id or slug', 'version with appId') are already fully documented in the schema. The description restates the same id-vs-version relationship without adding format examples or constraints, 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?

Names a specific verb+resource (fetch one release) and states its distinguishing scope — a single release identified either by id alone or by version+appId — which sets it apart from list_releases. The phrasing is slightly convoluted but the resource and lookup modes are unambiguous.

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 implies when to use it (when you need one release rather than a list) and explains the two lookup routes via 'by id or, with appId, by version.' It never names list_releases or another sibling as the alternative, so no explicit when-not guidance is given.

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