nexus_remove_badge_from_collection

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

The description adds useful behavioral context beyond the annotations: the operation requires moderator permissions, uses v2 GraphQL, and returns either {success} or an error string. It does not deeply describe side effects, but the mutation scope is clear from the name and annotations already indicate it is non-read-only and idempotent.

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 extremely concise: two sentences, purpose first, no filler, and the return behavior is clearly stated. Every part earns its place.

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 simple two-parameter mutation with complete schema descriptions, helpful annotations, and a stated return shape, the description is fully sufficient. The agent has everything needed to select and invoke the tool correctly.

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 already has 100% description coverage for both required parameters, including a helpful cross-reference for badge_id. The description itself does not add additional parameter semantics, so the schema carries the weight and baseline 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 clearly states a specific verb-resource pair: 'Remove a badge from a collection'. It also adds relevant context (moderator permissions required, v2 GraphQL) and is easily distinguished from the sibling tool nexus_add_badge_to_collection.

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 a clear prerequisite ('moderator permissions required') and the intended use case is obvious from the action. However, it does not explicitly name the alternative add tool or describe when not to use this tool, so it falls just short of full routing guidance.

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