search_mods

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

No annotations are provided, so the description must fully disclose behavioral traits. It only describes the search functionality and return values but does not mention safety (e.g., read-only), required permissions, or side effects. As a search tool, it is likely safe, but this is not explicit. The description lacks transparency beyond the obvious.

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?

The description is very concise, using a single sentence for purpose and a code block for parameter details. It is front-loaded with the main action and contains no unnecessary words. Every sentence adds value.

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?

The description covers the main function and output composition but omits explanation of the 'query' and 'limit' parameters. Given that an output schema exists, return values are adequately described. However, for a tool with 4 parameters and no annotations, the description could be more thorough. It is minimally complete.

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%, so the description must compensate. It explains two of the four parameters (item_tag and mod_type) with clear meaning. However, it does not describe the 'query' parameter (obvious from name but not explained) or 'limit' parameter. This partial coverage is adequate but not complete.

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 the tool searches for Path of Exile 2 affixes/modifiers by readable text, using a specific verb 'Search' and a distinct resource 'affixes/modifiers'. This distinguishes it from siblings like search_items (items) and search_passives (passives).

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 description implicitly tells when to use the tool (searching mods/affixes by text) and explains parameters, but does not explicitly state when not to use it or provide alternatives. The context from sibling tools helps, but no direct exclusions are given.

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