nexus_unlist_collection

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

Annotations already signal a non-read-only, non-destructive, idempotent operation. The description adds meaningful behavioral context beyond those annotations by stating the collection is hidden from public listings but the URL is kept, and by noting the response shape ('JSON {success} or an error string').

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: the core action and effect appear in the first sentence, and the return-format note is minimal. No filler or redundant wording is present.

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 with an output schema and annotations covering idempotence and destructiveness, the description is reasonably complete. It explains the key effect and return behavior, though it does not mention any ownership or authorization requirements, which may be contextual prerequisites.

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 coverage is 100% and the single parameter collection_id is already described as 'Collection ID.' with a minimum of 1. The description does not add further semantic detail about the parameter, which is acceptable because the schema carriers the full burden.

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 ('Unlist'), identifies the resource ('a collection'), and clarifies the effect ('hide from public listings, keep URL'). This clearly distinguishes it from similar collection tools like nexus_list_collection and nexus_discard_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 intended use case is implied by the description: use this when a collection should be hidden from public listings while retaining its URL. However, it does not explicitly name alternatives or state when not to use it, such as when relisting is desired via nexus_list_collection.

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