excel_read

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

Lacks annotations and does not describe return format, file selection mechanism, or any constraints. Merely says 'read data' without explaining how the spreadsheet is identified or what is returned.

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?

Single sentence with no wasted words, but lacks essential context. Conciseness is good but not at the expense of completeness.

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 no parameters and no output schema, the description is too minimal. It does not explain key aspects like file selection, sheet specification, or return format, leaving the agent underinformed.

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?

No parameters exist, so the description adds no semantic value. However, it fails to explain how the target spreadsheet is determined, which is a missing implicit parameter. Baseline 4 reduced due to omission.

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) and resource (Excel spreadsheet). It is unambiguous but does not distinguish from sibling tools like excel_create or excel_write_cell.

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 on when to use this tool versus alternatives. Does not mention that it is for reading data only, nor contrast with write or create tools.

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