search_excel

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

With no annotations, description carries full burden. Discloses case-insensitive substring search and result limit. No contradictions. Could mention whether it scans formulas or values, but adequate.

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?

Description is compact with clear structure: purpose sentence, behavior details, then parameter list with @param annotations. No wasted words.

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 the presence of an output schema, the description's mention of return format ('Formatted text with search results') is sufficient. Slightly incomplete on edge cases (e.g., behavior for empty results), but adequate.

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%, but description adds clear meaning for all three parameters: file_path (absolute path), query (text to search), sheet_name (limit to specific sheet or None). Adds significant value.

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?

Description clearly states it searches for text content across all cells, performing case-insensitive substring search and returning matching cells with coordinates and values. Distinguishes from sibling tools like read_excel_data by focusing on search.

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?

States result limit (100 results) and provides parameter descriptions. However, no explicit guidance on when to use this tool vs siblings like read_excel_data or list_sheets. Implied by purpose.

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