nexus_download_links

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

Annotations already cover read-only/idempotent/no-destruction and open-world scope. The description adds genuinely new context: links are temporary, they grant access, and they must not be shared. It also discloses the auth-tier requirement, which annotations do not.

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?

Three short sentences, no filler. The core action is front-loaded and the conditional requirement and security caveat follow in order of importance.

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?

No output schema exists, and the description covers the essential calling context: auth tier, required extras for free users, and the temporary/non-shareable nature of the result. It omits any indication of how many links come back or how long they last, which is a minor gap for a read-only 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?

Schema coverage is only 20% (only 'game' is documented), so the description must compensate. It does explain 'key' as a website NXM key and pairs it with 'expires', but says nothing about modId or fileId. Partial compensation keeps this at the baseline 3.

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?

States a specific verb and resource: 'Get temporary download URLs'. An agent immediately knows the output class. It does not name or contrast any sibling (e.g. vortex_download_mod), so it falls short of the top tier.

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?

Gives a clear conditional path: premium users can download directly, free users must supply the website NXM key and expires. That tells the agent which params apply under which account tier. No alternative-tool routing is offered, so not a 5.

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