excel_read_range_normalized

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

The description discloses two key behaviors: it reads data and virtually backfills merged cells, and it does not modify the source file. With no annotations, this provides minimal behavioral context. However, it omits details like handling of errors, empty ranges, or the structure of returned data.

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, concise sentence that front-loads the action and purpose. Every word earns its place without redundancy.

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 tool has five parameters and an output schema, the description covers the core functionality but lacks detail on parameter usage, output format, and edge cases. The presence of an output schema means return values need not be explained, but behavioral context remains incomplete.

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 tool description does not mention any parameters, even though the input schema has five properties. Schema description coverage is 0% as per context, meaning the description should compensate but does not. The schema itself has parameter descriptions in Chinese, but the tool description adds no value beyond that.

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 tool reads a specified area from an Excel file and virtually backfills merged cells without modifying the source. It uses a specific verb and resource, and distinguishes from sibling tools (excel_inspect, excel_profile_structure) which focus on structure/profile rather than data reading.

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 provides no guidance on when to use this tool versus alternatives. Sibling tools exist but there is no mention of trade-offs or conditions. The agent is left to infer usage solely from the tool name and description.

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