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

Annotations already declare it is a non-read-only, idempotent, non-destructive mutation. The description adds real value beyond that: the admin-only auth requirement and the fact that the mutation is reversible via shipped: false, neither of which is captured by 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?

A single tight sentence that front-loads the primary action, then the inverse case, then the permission constraint. Every clause carries information; nothing is padded.

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 100% schema coverage, an output schema, and annotations carrying the safety profile, the description fills its remaining obligations (auth requirement, inverse operation). It is essentially complete, though it could note side effects on release contents.

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 meaning the schema omits – it explains that setting 'shipped' to false un-ships the release, whereas the schema only says 'Defaults to true'. It adds no detail for project/release keys, which the schema already covers.

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 ('Marks a release shipped') and clarifies both the forward and inverse operation. It is clearly distinct from the closest sibling create_release, which creates rather than transitions state, though it never names that sibling explicitly.

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?

Covers both directions of the operation (ship and un-ship via shipped: false) and adds an 'Admins only' precondition, which is genuinely useful context. However, it gives no explicit when-to-use-vs-alternatives guidance or mention of prerequisites/conflicts relative to create_release.

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