get_mods

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

No annotations provided, so description carries full burden. It discloses that this is a list operation with pagination and filtering. It mentions prerequisites and supports multiple game IDs. It does not discuss rate limits or error states, but is transparent about the read-only nature and required inputs.

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?

Well-structured with sections for prerequisite, workflow, and parameter details. It is front-loaded with the purpose. While somewhat lengthy, every sentence adds value given the zero schema coverage.

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?

Given the tool complexity (6 parameters, prerequisites, sorting, filtering), the description covers the essential workflow and parameter details. It also provides a URL pattern for mod details, which aids in using the output. Lacks explicit return format description, but the URL hint compensates.

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 has 0% description coverage, so description adds significant value. It explains each parameter: page, page_size, game_id (single/multiple), search, order (with enum mapping), and time (with enum mapping). This goes well beyond the schema titles.

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 clearly states it retrieves a list of mods, with a specific prerequisite (game ID from get_games). It distinguishes from siblings like get_mod_detail (single mod) and get_games (game list).

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?

Explicitly states prerequisite (must call get_games first) and provides a typical workflow. Lists multiple filters and sorting options. However, it does not explicitly mention when not to use this tool or alternatives.

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