nexus_update_mod_direct_download

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

Annotations already mark this as a non-read-only, idempotent mutation; the description adds the critical OAuth-only constraint and the failure mode under apikey-only auth. It also discloses that the response is a JSON payload or an error string. This goes beyond what annotations alone reveal.

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: a purpose sentence, an auth warning, a use case, and a return line. There is no filler or redundant restatement of the schema. It is front-loaded with the action.

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, the description covers purpose, auth prerequisite, failure mode, and return behavior. The output schema covers exact return fields, so nothing critical is missing. It is complete enough for an agent to decide and invoke safely.

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 schema documents both parameters at 100% coverage, so the baseline is 3. The description adds the ownership requirement ('your own mod', 'mod authors'), which clarifies that mod_uid must belong to the authenticated user. The enabled boolean is also self-explanatory from the first sentence.

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 first sentence states the exact operation: enabling or disabling direct (no-ads) downloads for the user's own mod, and scopes it to the v2 GraphQL API. This is clearly distinct from the many get/download siblings and from user-preference mutations. The annotation title reinforces the toggle semantics.

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?

It explicitly states the precondition that OAuth login is required and that apikey-only auth will be rejected, which tells an agent when not to invoke it. It also identifies the intended audience (mod authors automating release pipelines). It doesn't name a sibling alternative, but no sibling appears to provide the same toggle, so the context is clear.

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