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

Annotations already declare readOnlyHint, idempotentHint, and non-destructiveness. The description adds useful behavioral detail beyond them: a hard 50-row cap, omission of empty Data columns, and omission of created_at and updated_at. It could still mention ordering or pagination behavior, but it adds meaningful context.

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 short, front-loaded, and every sentence carries information about search behavior or return formatting. There is no wasted language.

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 read tool with no output schema and rich annotations, the description is adequate on return behavior. However, with 0% schema description coverage, it should explain the query and sheet_number parameters to be complete enough for reliable invocation.

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 explain the two parameters. It implies that 'query' is a search string but gives no syntax or matching semantics, and it does not mention 'sheet_number' at all, leaving both parameters under-specified.

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 states a specific verb and resource: searching the item table. It is clearly distinguishable from mutation tools like create_item or delete_item, but it does not differentiate itself from sibling read tools such as list_items or get_item, leaving the agent to infer which read operation to use.

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 gives no guidance on when to use search_items versus list_items, get_item, or other query-like tools. It also does not state whether this is for fuzzy text matching, exact lookup, or browsing by sheet.

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