nexus_close_collection_bug_report

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=true, so the core safety profile is covered. The description adds the v2 GraphQL channel and the returned fields (id, status, closureReason, closedAt), but it does not explain irreversibility or ownership requirements beyond 'your collection.' There is no contradiction with the annotations.

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: one sentence states the operation and one block states the return shape. There is no filler or redundant repetition of the schema.

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 two-parameter mutation with full schema coverage, a return shape, and safety annotations, the description provides enough context to invoke the tool correctly. It could be stronger with explicit authentication/ownership guidance, but 'your collection' already signals the main prerequisite.

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%, so the schema already documents both parameters and the closure_reason enum is self-explanatory. The description introduces no additional parameter-level meaning, which is acceptable given the full schema coverage baseline.

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 action ('Close') on a specific resource ('a bug report on your collection') and distinguishes it from the many collection-related sibling tools. The 'via v2 GraphQL' qualifier and 'your collection' scope make the operation concrete and unambiguous.

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 opening phrase clearly indicates when to use the tool: when closing a bug report on the authenticated user's own collection. No sibling tool appears to duplicate this action, so an explicit alternative is not necessary, though the description does not spell out exclusions or prerequisites such as collection ownership.

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