nexus_mod_files

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive behavior, so the safety profile is covered structurally. The description contributes 'Paginated locally', a genuinely useful behavioral note about pagination semantics, but says nothing about result shape, rate limits, or failure modes.

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?

A single tight sentence with the core purpose front-loaded and zero filler. Slightly terse given the tool's undocumented parameters, but structurally efficient.

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?

There is no output schema, so the description must carry the full burden of explaining what is returned, and it does not describe the file/version record shape. Combined with low parameter coverage and no logical sibling routing, it is adequate but leaves real gaps for an agent invoking it correctly.

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 description coverage is only 25% — only 'game' is documented in the schema, while 'modId', 'limit', and 'offset' carry no descriptions. The description does not compensate: it never explains modId's meaning or the limit/offset pagination contract beyond the vague phrase 'paginated locally'.

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 ('List downloadable files and versions for a mod') and adds a scoping note about legacy game-scoped file IDs, which implicitly distinguishes it from the nexus_v3_files sibling. Clear and actionable, though the legacy-vs-v3 distinction is hinted rather than stated outright.

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 parenthetical 'legacy game-scoped file IDs' implies this is the legacy-API variant and the v3 siblings are the modern alternative, but there is no explicit when-to-use or when-not-to-use guidance. Usage is inferable from context rather than stated.

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