search_in_sheet

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

The description only states that it searches for matching cells, providing no details on exact vs. partial matching, case sensitivity, return format, or limits. The readOnlyHint=true annotation is present but the description adds no behavioral context beyond that.

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, but it is under-specified rather than appropriately concise. It repeats information already present in the tool name and provides no additional useful content, so it does not earn its place.

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?

The tool has 5 parameters and no output schema, yet the description gives no information about search behavior, return format, matching rules, or limitations. It is completely inadequate for a tool with this complexity.

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%. The description mentions no parameters and does not explain the meaning or behavior of query, exact, max_results, filepath, or sheet_name. It completely fails to compensate for the schema's lack of descriptions.

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 'Search for cells matching a value in a worksheet' essentially restates the tool name 'search_in_sheet' and the annotation title 'Search Cells'. It uses the same verb and resource without adding scope, matching semantics, or differentiation from sibling tools like query_table or read_data_from_excel.

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 is given about when to prefer this tool over alternatives. The sibling list includes many reading/searching tools (e.g., read_data_from_excel, query_table), but the description does not mention any differentiators or exclusions.

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