list_mods

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

Annotations already declare the full safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description contributes useful structural context by distinguishing two data sources (modsStorage cache vs modsStorage/draft with a `draft` field), but says nothing about pagination, limits, or developer-mode prerequisites beyond the passing adjective.

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 that leads with the core action and packs in the return structure and filter semantics without filler. Dense but every clause carries information.

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?

An output schema exists, so return-value detail is not strictly required, yet the description still sketches the shape of both result groups. Combined with the filter semantics, an agent has enough to call the tool correctly; only ordering/limits are unaddressed.

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% and the lone `query` parameter is undocumented in the schema, so the description carries the burden. It does that reasonably well by stating the filter is optional and matches a substring on id, which is meaning the schema alone does not convey.

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 resource (mods), and goes further by enumerating what is listed: published cache entries plus developer-mode drafts. This is more specific than a bare 'list mods', though it never names nearest siblings like get_mod or search_mod_code to sharpen the boundary.

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?

Usage is implied: enumerate mods, optionally narrow by id substring. There is no explicit when-to-use guidance versus get_mod (single mod) or the search_* tools, and no stated exclusions. The filter note is the only operational context provided.

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