search_ge_items

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

No annotations are provided, so the description carries the full burden. It discloses match type and return fields, which adds value. However, it does not mention pagination behavior, rate limits, or any other behavioral constraints beyond what the input schema implies.

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, no wasted words, front-loaded with the core purpose. Efficient and clear.

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's simplicity, full schema coverage, and lack of output schema, the description covers all essential aspects: purpose, matching behavior, and return data. No gaps are apparent.

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?

Input schema coverage is 100%, so baseline is 3. The description adds context by explaining the query parameter uses exact/prefix/substring matching, and clarifies return fields not in schema. This surpasses baseline.

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 Grand Exchange tradeable items by name, specifies the matching type (exact/prefix/substring), and lists returned fields (IDs, names, buy limits, alch values). It is distinct from sibling tools which target different data types (e.g., search_npctypes, get_ge_latest).

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 implies usage when searching for GE items by name, but lacks explicit guidance on when to use this tool versus alternatives like get_ge_latest for prices or other search tools for different game data. No exclusions or when-not use cases are mentioned.

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