Excel MCP Server

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

Annotations indicate destructiveHint=true and readOnlyHint=false, suggesting potential side effects, but the description doesn't clarify what gets destroyed or modified (e.g., file locks, temporary data). It adds 'with pagination' as useful context beyond annotations, but misses details like rate limits or authentication needs.

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, efficient sentence with zero waste—'Read values from Excel sheet with pagination' is front-loaded and every word earns its place by specifying action, resource, and a key behavioral trait.

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 5 parameters, no output schema, and annotations with mixed hints (destructive but not read-only), the description is minimal. It covers the core purpose and pagination but lacks details on return format, error handling, or side effects, leaving gaps for a tool with potential destructive behavior.

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 100%, so the schema fully documents all 5 parameters. The description adds no additional meaning about parameters beyond implying pagination relates to 'range', which is already covered in the schema's default note. Baseline 3 is appropriate as the schema handles the heavy lifting.

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 the action ('Read values') and resource ('Excel sheet'), with 'with pagination' adding a key behavioral aspect. It distinguishes from siblings like excel_write_to_sheet (write vs. read) and excel_describe_sheets (metadata vs. values), though it doesn't explicitly name alternatives.

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 provided on when to use this tool versus alternatives like excel_describe_sheets for sheet metadata or excel_copy_sheet for duplicating content. The description implies reading data but lacks context about prerequisites or exclusions.

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