nexus_get_file_hash

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

Annotations already declare the operation as read-only, idempotent, non-destructive, and open-world, so the description only needs to add context beyond those. It adds that this is a v2 GraphQL endpoint and that the result is a JSON list with specific fields, which is useful but modest; no rate-limit, pagination, or exact-match caveats are disclosed.

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 short, front-loaded with the core purpose, and the return list is presented compactly. Every sentence contributes either to what the tool does or what it returns.

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 one-parameter read-only lookup with full schema coverage and an output schema, the essential operational context is present. However, the description does not address the ambiguity with nexus_search_by_md5, so the contextual picture is not fully complete for an agent choosing among similar tools.

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% and the md5 parameter is described as 'MD5 hash of the file,' which is unambiguous. The tool description restates the lookup concept but adds no additional parameter semantics beyond the schema, so the baseline of 3 applies.

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 states a specific action ('Look up which mod file matches an MD5 hash') and clearly identifies the resource and purpose. It is clear, but it does not explicitly distinguish itself from the similarly named sibling nexus_search_by_md5, so it falls short of full differentiation.

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?

There is no guidance about when to use this tool versus alternatives such as nexus_search_by_md5, nexus_get_file_hashes, or nexus_get_file_info. The description relies entirely on the tool name and the one-line purpose, leaving selection to inference.

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