nexus_discard_tag

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds valuable context: the operation is a soft-delete rather than a hard delete, moderator permissions may be required, and the response is either {success} or an error string. This complements the annotations without contradicting them.

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-loads the action and resource in the first clause. The return-value note is useful, though the parenthetical 'via v2 GraphQL' is somewhat redundant and could be omitted without losing meaning.

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 destructive operation, the description covers the action, the authorization caveat, and the return shape, while the schema fully documents the parameter. It lacks usage differentiation against related tag tools, but that gap is already reflected in the usage_guidelines score, and the overall complexity is low.

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%: the single parameter tag_id is fully documented as an integer with minimum 1 and the description 'Tag ID.' The tool description adds no parameter-specific detail beyond the schema, so 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 uses a specific verb ('Discard') and resource ('a tag'), clarifies that the operation is a soft-delete, and identifies the v2 GraphQL interface. This clearly distinguishes it from related tag operations in the sibling list such as create_tag, update_tag, block_tag, and get_tag_by_id.

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?

There is no guidance on when to use this tool versus alternatives like nexus_block_tag, nexus_update_tag, or nexus_unblock_tag. The only condition mentioned, that moderator permissions may be required, is a prerequisite rather than a selection criterion.

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