nexus_get_files_v2

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds useful behavioral context beyond annotations: it uses the v2 GraphQL API, is quota-free against the v1 pool, and returns a specific JSON shape.

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 purpose is front-loaded and the return format is useful, but the description is somewhat redundant: 'Backed by the v2 GraphQL API' repeats the first sentence, and 'quota-free on the v1 pool' repeats the earlier rate-limit statement. It is concise overall, but not maximally tight.

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 simple two-parameter, read-only tool with full schema coverage, rich annotations, an output schema, and a clear sibling comparison, the description provides all information an agent needs to select and invoke the tool 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?

The input schema has 100% description coverage for both parameters, including the important note that domain_name is a lowercase URL slug, not the display name. The description does not need to repeat parameter semantics, so the baseline of 3 is appropriate.

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 a specific verb and resource: 'Get the complete file list of a mod via v2 GraphQL.' It also explicitly distinguishes itself from the sibling tool nexus_get_mod_files by noting it returns the same data but from v2, so an agent can immediately tell them apart.

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 description names nexus_get_mod_files as the alternative and gives a concrete selection criterion: the v2 API does not consume the v1 REST rate-limit quota. It does not explicitly state when not to use this tool, but the usage context is clear enough.

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