nexus_get_collection_revision_upload_url

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

The description adds that this is a presigned-URL request and that the response contains {url, uuid}, which is useful. Annotations already disclose readOnlyHint, idempotentHint, openWorldHint, and non-destructiveness, so the bar is lower; the description does not contradict these but also does not reveal additional behavior such as URL expiry, upload method, or authentication requirements.

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 first sentence states the operation and resource, and the second gives the response shape. No filler or redundant material exists.

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 zero-parameter, read-only request tool with annotations and an output schema, the description is largely sufficient. It clearly identifies the purpose and return shape; a slight gap is that it does not explain how the returned URL/uuid fit into the broader collection-revision workflow or compare with the sibling media-upload tool.

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 has zero parameters and schema description coverage is effectively complete, so there are no parameter semantics to document. Per the 0-param baseline, a score of 4 is appropriate; the description correctly implies there is nothing for the caller to supply.

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 precise verb ('Request'), a concrete resource ('presigned URL for uploading a collection revision bundle'), and protocol context ('v2 GraphQL'). This differentiates it from the sibling media-upload tool by naming the specific bundle type, so an agent can identify it without ambiguity.

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 resource mention makes the intended use clear: this is for obtaining an upload URL for collection revision bundles. However, there is no explicit guidance about when not to use it or how it relates to alternative upload/request tools such as nexus_request_media_upload_url; the usage context is implied rather than stated.

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