search_items

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

With no annotations provided, the description carries the full burden. It discloses the behavioral trait of returning matching bases with specified fields, which implies a read-only operation. It does not mention authentication, rate limits, or search semantics (e.g., exact vs. fuzzy), but given the output schema existence, the return structure is defined elsewhere.

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 two sentences with no wasted words. It front-loads the main purpose, then provides return info and a pointer to an alternative. Very concise 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 the tool has 3 parameters (none required) and an output schema, the description covers the core functionality, return values, and an alternative. It lacks explicit parameter format details but is reasonably complete for a search tool.

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%, so the description must compensate. It adds meaning by indicating that 'query' searches by name/tags and 'item_class' filters results. However, the 'limit' parameter and any default behavior are not described, leaving some ambiguity.

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 Path of Exile 2 item bases by name/tags with optional item class filtering. It specifies the return fields (name, item_class, drop_level, tags) and distinguishes itself from sibling get_item by directing users to that tool for full detail.

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 provides a clear context for when to use this tool (searching by name/tags) and explicitly mentions an alternative (get_item) for full details. However, it does not specify when not to use this tool versus other siblings like search_mods.

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