nexus_unblock_tag

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false), the description discloses that this operation has no public side effect and that reads can lag several seconds after success. It also states the return shape. This is meaningful behavioral context worth credit.

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 description is compact and front-loaded with the primary purpose, then gives the key behavior caveat, and ends with the return format. Each sentence earns its place; there is no redundant filler.

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 single-parameter mutation tool, this definition is complete: it explains what the tool does, its side-effect profile, a critical eventual-consistency caveat, and the expected output. The output schema exists, so no further return-value documentation is needed.

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?

The input schema fully documents tag_id as an integer with minimum 1 and description 'Tag ID to unblock.' The tool description adds no extra parameter-level meaning, but since schema coverage is 100%, the baseline of 3 is appropriate.

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 description states a specific verb ('Unblock') and resource ('previously blocked tag') and mentions the v2 GraphQL mechanism. This clearly distinguishes it from sibling tools like nexus_block_tag and nexus_get_blocked_tags without needing to inspect their 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?

The description gives clear context: it is a personal-preference operation with no public side effect, and it warns that list reads via nexus_get_blocked_tags can lag, so re-reading immediately is not reliable. It doesn't explicitly say 'do not use this for public tag state,' but the personal-preference scoping implies the boundary.

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