read_excel_data

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

The description explains hidden rows/columns are skipped by default and kept as [HIDDEN-REF] if depended on by visible formulas. It also explains formatting markers. However, with no annotations, it doesn't state that the tool is read-only or safe, nor does it cover exceptions like missing files.

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 concise and front-loaded with the main purpose. The @param list is clear, though could be slightly more integrated. No superfluous sentences.

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 output schema existence, return value details are not fully required, but the description lacks error handling for missing files or sheets. It adequately covers pagination and hidden cells but misses edge case behaviors.

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?

The @param section in the description fully explains each parameter's meaning and default, compensating for the 0% schema coverage. For example, 'sheet_name: None = first/active sheet' and 'include_hidden: Set true to also read hidden rows/columns.'

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 'Read cell data from an Excel sheet with pagination for large files,' specifying the action and resource. It distinguishes from sibling tools like 'read_full_content' (no pagination) and 'search_excel' (searching).

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 implies use for large files via pagination but does not explicitly state when to use this tool versus alternatives like 'read_full_content' for small files. No prerequisites or when-not-to-use guidance is provided, leaving some ambiguity.

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