list_mod_versions

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

With no annotations, the description carries the load and does disclose behavior beyond the signature: newest-first ordering, that instanceId adds matchesInstance annotations to results, and that an auto-picked latest release is shown. It omits whether the call is read-only or requires a network/auth context, which is the remaining gap.

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 short sentences with zero filler; the core purpose, the instanceId modifier, and the downstream install_mod link are ordered by importance.

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 two-parameter read of modest complexity with no output schema, it covers the essential behaviors including result ordering and the extra fields instanceId produces. A brief note on project identifier format or read-only nature would close the remaining gap.

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 0%, so the description must compensate and largely does: instanceId's effect on the response is spelled out and 'project' is framed as a Modrinth project. The identifier format for 'project' (slug vs ID) is not stated, keeping it out of the top band.

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 a Modrinth project's versions') plus ordering ('newest first'), which cleanly separates it from list_mods and list_versions in the sibling set. It does not explicitly contrast itself with list_versions, so differentiation is implied rather than stated.

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?

Explains the instanceId variant and routes the agent forward explicitly: 'Use a version's id with install_mod to pin or roll back a version.' This is a concrete workflow cue, but there is no statement of when not to call it or which sibling to prefer for other version lookups.

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