search_items

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

With no annotations provided, the description bears the full burden of behavioral disclosure. It only states the search scope and criteria, but does not mention read-only behavior, return format, pagination, or match semantics (e.g., partial vs. exact). This is a minimal disclosure 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?

The description is a single concise sentence, front-loaded with the action and resource. It contains no filler and fully uses its words effectively.

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?

For a simple search tool with one parameter and no output schema, the description is adequate but incomplete. It does not explain what the tool returns (e.g., list of objects, IDs) or any constraints like result limits. Sibling tools like get_items suggest alternative retrieval methods, but no guidance is offered.

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?

The schema has 0% description coverage, so the description must compensate. It does convey that the searchTerm is used to match against name or description, which adds meaning beyond the bare schema. However, it does not specify match type, case sensitivity, or how multiple fields are combined.

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's function: searching items, weapons, and armors by name or description. This is a specific verb-resource combination that distinguishes it from sibling tools like get_items or create_weapon, which have different purposes.

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 when to use the tool (when searching items/weapons/armors by name/description) but does not explicitly contrast it with alternatives like get_items or get_weapons. No exclusions or when-not-to-use guidance is provided.

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