nexus_list_collection

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

Annotations already indicate this is a mutating (readOnlyHint=false), non-destructive, idempotent operation. The description adds useful behavioral context: it publishes the collection, requires ownership, and returns JSON {success} or an error string. This goes beyond 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-loaded: the action appears in the first line, followed by key eligibility context and a brief return note. Every sentence contributes value, and there is no filler or redundant re-explanation 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 simple single-parameter mutation with an output schema and helpful annotations, the description covers the essential operational facts: what it does, who can use it, precondition, and return shape. It does not enumerate edge cases, but nothing critical is missing for correct invocation.

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 already has a clear 'Collection ID.' description. The tool description does not add new parameter-level meaning, so the baseline 3 applies.

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 — 'List (publish) a currently unlisted collection' — with a clear resource and a parenthetical clarifying that 'list' means publish, not fetch. It is distinguishable from the sibling nexus_unlist_collection, though it does not explicitly name that sibling.

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 clear context: the collection must be currently unlisted and the caller must own it. It does not explicitly mention alternatives such as nexus_unlist_collection or nexus_publish_revision, and it does not state when not to use this tool, so usage guidance is implied rather than explicit.

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