nexus_get_mod_files

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

Annotations already establish readOnlyHint and idempotentHint, so the description's job is lighter. It adds meaningful behavioral context by documenting the JSON shape, the update-chain relationship, and the category_id mapping, which an agent needs to interpret results. No contradictions with annotations.

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, front-loaded with the purpose, and uses a short structured return block for the update chain and category mapping. Every sentence carries information and no filler is present.

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 read-only list operation, the description plus annotations and output schema cover the required inputs, the returned shapes, and category semantics. No critical detail needed to invoke the tool correctly is missing.

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 100%: domain_name, mod_id, and category are already documented in the schema. The description adds category-id semantics for interpreting results, but does not add parameter-level usage detail beyond the schema, so it meets the baseline without exceeding it.

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 opens with a specific verb and resource: 'List all files attached to a mod', then enumerates return fields (versions, sizes, upload dates, update chain). This clearly distinguishes it from sibling tools like nexus_get_file_info or nexus_get_download_link, which target individual files or downloads.

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 phrase 'List all files attached to a mod' supplies clear when-to-use context, and the return details ('update chain') signal a bulk listing use case. It does not explicitly contrast with alternatives or state exclusions, so it falls short of a full 5.

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