read_excel_data

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

Discloses pagination support and return format ('formatted text table'), which are key behaviors. Lacks error handling or performance details, but adequate for a read-only tool with no annotations.

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?

Concise with a clear primary line, then details on return and pagination, followed by one-line param descriptions. No unnecessary 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?

Covers main functionality, pagination, and return format. With an output schema present, description is sufficient for agent use, though might omit error conditions.

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?

Adds meaning beyond schema: explains file_path as absolute path, sheet_name default behavior, start_row as 1-indexed, and max_rows default. Compensates for 0% schema coverage effectively.

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?

Clearly states 'Read cell data from an Excel sheet with pagination for large files.' The verb 'Read' and resource 'Excel sheet' are specific, and pagination distinguishes it from siblings like 'read_full_content' and 'list_sheets'.

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?

Implies usage for large files via pagination mentions, but does not explicitly state when to use versus alternatives or exclude cases. No comparison with siblings provided.

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