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

Annotations only declare it as a non-destructive, non-read-only write; the description goes well beyond that with permission rules (members, release managers, project admins; viewers 403), a prerequisite failure mode (400 for a missing/already-released target), cascade semantics (an epic's children follow unless they name another release), and scope-history side effects once the baseline is locked. The 409 version_conflict recovery protocol is spelled out with `details.current` / `details.current_version` and an explicit 'never overwrite blindly' rule.

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?

Front-loaded and generally well organized, but the title sentence is repeated verbatim as the first line, and the 'after the release's baseline is locked / kept in the scope history' idea is stated twice in near-identical wording. Tightening those duplicates would cut noticeable length without losing information.

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 and a 5-parameter write tool that cascades to epic children, the description covers prerequisites, permissions, error paths and recovery, which is most of what an agent needs. It never says what a successful response contains (e.g. the new version), leaving that to be inferred from the 409 guidance.

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 80%, so the baseline is 3; the description adds real meaning on top by tying `version` to a mandatory read-before-write flow and explaining the `release: null` removal case and the timing of `reason` relative to the baseline lock. It doesn't add format or identity detail for `project_key`/`issue_key` beyond what the schema already documents.

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 — put an issue (or an epic with its children) into a release, or take it out via `release: null`. It also positions itself against siblings by describing the relationship to `update_issue` and routing bulk work to `add_to_release`, so an agent can distinguish it without opening other schemas.

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?

Gives explicit preconditions (the release must exist and not be released yet; call `get_issue` first and pass its `version`), an explicit alternative for the bulk case ('use add_to_release … instead of calling this once per issue'), and guidance on when to supply `reason`.

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