List ModDB comments

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

readOnlyHint=true already tells the agent this is a safe read. The description usefully adds the sort order and the shape of the returned identifiers, but says nothing about pagination beyond the schema's limit, rate limits, or how deleted/hidden comments are treated by default. Adequate but not rich.

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?

Two compact sentences, zero filler, with the core action and ordering front-loaded ahead of the identifier formats and return-value note.

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?

With no output schema, the description compensates by stating that comment ids are returned and what they feed into. Minor gaps remain around pagination behavior and how to page past the limit, but nothing essential to invoking the tool 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%, so the schema already explains the accepted mod identifier forms (alias, numeric id, URL) and the limit/include_deleted semantics. The description restates the identifier forms without adding syntax or edge-case detail, so the baseline 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?

States a specific verb and resource ('List comments on a mod's ModDB page') plus ordering ('newest first'). It is clearly distinguishable from the reply_to_comment, edit_comment and delete_comment siblings, which mutate the same resource.

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?

Names the downstream tools that consume the returned comment ids (reply_to_comment, edit_comment, delete_comment), which implicitly defines the workflow context for calling this tool. It does not state when *not* to use it or name an alternative listing tool, so it stops short of a 5.

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