search_items

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

Since no annotations are provided, the description carries the full burden of disclosing behavioral traits. 'Search' implies a read-only operation, but the description does not mention result ordering, match behavior (e.g., partial vs. exact), default limits, or any side effects. The phrase 'optional filters' hints at filtering capabilities but does not detail them.

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 short sentence, which is concise but under-specified. Given the tool has five parameters and no schema descriptions, this brevity sacrifices necessary detail, making it more anemic than appropriately concise.

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?

With five parameters, no annotations, and a 0% schema coverage, the tool is underspecified. The description does not explain the purpose of each filter, how results are returned (although an output schema exists), or when to use this tool vs. sibling tools. The presence of an output schema mitigates some need for return-value detail, but the overall context remains incomplete.

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%, and the description fails to compensate. It only mentions 'optional filters' without naming any of the actual filter parameters (status, item_type, jlpt_level) or explaining the required 'query' parameter or 'limit'. The function's parameter semantics are almost entirely unsupported.

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 action ('Search') and resource ('personal Japanese knowledge items'), making its primary purpose unambiguous. However, it does not explicitly differentiate it from sibling tools like get_due_reviews, which also involves searching/fetching items.

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 offers no guidance on when to use this tool versus alternatives such as get_due_reviews or upsert_item. It only implies usage for searching with filters, without any exclusions or contextual prerequisites.

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