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

Annotations already declare idempotentHint=true, destructiveHint=false and readOnlyHint=false, so the safety profile is covered. The description adds non-obvious context beyond that: exactly which fields are mutated and the permission model governing who may perform it.

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?

Two sentences, zero padding, with the action and its observable effect front-loaded and the permission constraint last. Every clause carries information the agent needs.

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 one-parameter mutation with full schema coverage and annotations covering idempotency and safety, the definition covers purpose, effect and authorization. It stops short of saying what error surfaces when an unauthorized caller attempts the release, a minor gap for a non-destructive, idempotent tool.

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% and the single `id` parameter is thoroughly documented (UUID or human-readable TEAM-123, case-insensitive, UUID required on cross-workspace collisions). The description adds nothing about the parameter, so the 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?

States a specific verb (release) on a specific resource (issue) and spells out the concrete effect: clearing agentWorkingBy/agentWorkingSince so the issue no longer shows as 'en curso' in the UI and to other agents. That effect statement cleanly separates it from siblings like claim_issue and change_issue_state.

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?

Names the authorization precondition (only the agent who claimed it, or a workspace admin), which tells the agent when the call will succeed. It implies the trigger (finishing/releasing a claimed issue) but does not explicitly name claim_issue or a state-change alternative as the contrasting tool.

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