Mod files

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true. The description adds real behavioral context beyond that: the default exclusion of archived/old versions and the upload history. It omits pagination/return-shape details, but the safety and default-filtering profile is well covered.

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 tight sentences, all front-loaded: purpose first, then default behavior, then the alternative route. No filler or repetition.

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 tool with a fully-described schema and no output schema, this covers purpose, defaults, single-file mode, and the alternative route. Missing only minor operational detail (e.g. pagination), which is not required given the annotations and schema.

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 high (88%), so the schema does the heavy lifting and baseline is 3. The description nonetheless adds meaning by explaining the file_id single-file path and the default filtering behavior that governs include_old/include_history, edging above baseline.

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 the files published for a mod'), and names a sibling (nexus_mod_overview) with the condition that selects it. An agent can distinguish it from nexus_get_mod and nexus_mod_overview without opening any schema.

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 clear context (default filtering of old versions/history) and explicitly routes to nexus_mod_overview 'for a complete picture', plus when to pass file_id. This is strong routing guidance; it stops short of enumerating every when-not scenario, so 4 rather than 5.

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