Search items

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

With no annotations, the description carries the behavioral burden and does well: it discloses substring matching, optional filters, and that returns are compact summaries rather than full item data. It does not discuss pagination or error behavior, but for a read-only search tool the key behavioral traits are covered.

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?

Three tightly written sentences with no filler: purpose and matching semantics first, then optional filters, then return behavior and the pointer to get_item. Every sentence earns its place.

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 there is no output schema, the description adequately explains return values (compact summaries with id, name, prices) and the fallback to get_item. The remaining details like defaults and limits are already fully covered by the input schema.

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%, so the baseline is 3, but the description adds real value beyond the schema: it defines query as substring matching over name/shortName/normalizedName, clarifies what the type filter values mean, and specifies that trader matches buy or sell relationships.

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 ('Search'), resource ('Escape from Tarkov items'), match semantics ('name/short name ... substring match'), and optional filters. It clearly distinguishes itself from get_item by noting that it returns compact summaries while get_item provides 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 says to use get_item when full detail on one item is needed, giving a clear alternative condition. It does not mention other sibling tools like search_barters or search_crafts, but the target resource and filter behavior are clear enough to route an agent correctly.

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