Search Mods

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

No annotations exist, so description must disclose behavior. It mentions returned paginated results and support for various filters but omits side effects, mutability, or rate limits. Adequate but not thorough for a search tool.

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 sentences with no wasted words. First sentence states purpose, second adds details on query and filtering. Front-loaded and efficient.

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 10 optional parameters, no output schema, and no annotations, the description covers the main functionality and pagination. Could mention maximum per_page limit or that multiple filters combine with AND, but not critical.

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 100% with each parameter well-described. The description adds value by summarizing the filtering capabilities and grouping parameters (e.g., 'filtering by name, category, SPT version, Fika compatibility') which helps organize the parameter set.

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?

Description clearly states the tool searches and filters SP-Tarkov mods with specific verb 'Search and filter' and resource 'SP-Tarkov mods'. It distinguishes from siblings like 'get_mod' (single mod retrieval) and 'search_addons' (different 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?

Provides clear context for when to use: full-text search and filtering by multiple criteria. Though it doesn't explicitly mention when not to use, sibling tool names (e.g., get_mod, check_mod_updates) imply alternatives.

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