nexus_add_badge_to_collection

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

The description discloses that the operation requires moderator permissions, communicates the transport ('via v2 GraphQL'), and specifies the return shape ('JSON {success} or an error string'). These details add behavioral context beyond the annotations, which already indicate idempotency, non-read-only, and non-destructive behavior. No contradiction with annotations exists.

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 concise and front-loaded with the core action. Every sentence adds value: the action, the permission requirement, the transport, and the return format. There is no redundant filler or unnecessary length.

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?

Given the tool's simplicity (2 required scalar params, output schema present, annotations covering idempotency and safety), the description is largely complete. It covers the permission requirement and return value. The only notable gap is the absence of explicit alternative guidance, which is minor for such a straightforward mutation and does not significantly impair an agent's ability to use it 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 provides 100% description coverage for both parameters, with badge_id pointing to nexus_get_badges and collection_id described as 'Collection ID.' The tool description itself adds no additional parameter semantics, so the baseline of 3 is appropriate rather than a higher score.

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 and resource: 'Award a badge to a collection.' This clearly identifies the action and target, and the inclusion of 'moderator permissions required' adds important context. It is distinct from the sibling nexus_remove_badge_from_collection by virtue of the opposing action, so an agent can tell them apart without opening 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 provides no guidance on when to use this tool versus alternatives. It mentions a prerequisite ('moderator permissions required') but does not reference sibling tools like nexus_remove_badge_from_collection or explicitly state that this is the tool to use when awarding a badge. Usage context is left entirely to inference from the tool name and action.

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