list_blocked_mods

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

With no annotations, the description carries the full burden and does add useful domain context: it explains what 'blocked' means (files awaiting manual download). It says nothing about permissions, side effects (apparently none, read-only), pagination, or what the entries look like.

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?

A single, front-loaded sentence with zero filler. Slightly terse rather than verbose; the only waste is none at all, though the brevity comes at the cost of the missing usage guidance.

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?

A simple one-parameter read tool with no output schema, so the description should at least sketch what a returned entry contains (file name, mod, download URL). It doesn't, leaving the agent to discover the return shape by calling it.

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 0% for the single required instanceId parameter, so the description must compensate. Saying 'for an instance' does loosely bind the parameter to its meaning, but it adds no format details; the param name is largely self-explanatory given the sibling tools.

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 (List) and a specific resource (CurseForge files awaiting manual user download) scoped to an instance. It is distinguishable from most siblings, though it does not explicitly name resolve_blocked_mods, the tool that clearly overlaps.

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 phrase 'waiting for the user to download them manually' implies this is the read-only inspection step before resolve_blocked_mods, but no alternative is named and there is no explicit when/when-not guidance. Usage must be inferred from domain knowledge.

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