search_items

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

The description adds behavioral details beyond the schema: the query uses contains logic and supports wildcards. However, with no annotations provided, it does not disclose whether the tool has side effects (likely not), authentication requirements, or result limits. It is adequate but not thorough.

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?

One concise sentence in Japanese that efficiently conveys the tool's function and key detail (wildcard support). No wasted words, though a bit more structure could help.

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 no output schema and the tool's simplicity, the description is minimally adequate. It explains the search mechanism but does not mention what the tool returns (e.g., a list of items), leaving some ambiguity about the response format.

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 that 'query' maps to a contains parameter with wildcards, adding meaning. However, 'project_id' is not described, leaving its role partially unclear. The description adds value but not fully.

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 it performs keyword search on items and explains that query maps to a contains parameter with wildcard support. However, it does not specify the resource being searched (items) explicitly, but it's implied by the tool name and context.

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?

No guidance on when to use this tool versus alternatives like get_items (which likely lists all items). The description only explains how the tool works, not when it's appropriate.

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