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

With no annotations provided, the description fully carries the behavioral disclosure burden. It reveals the maximum read size, that empty cells are omitted, that both values and formulas are returned, and critically warns that without the sheet parameter the result may quietly reference the wrong sheet. This is rich, honest behavioral context.

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 three compact sentences with no filler. The primary action and range format are front-loaded, followed by the critical sheet caveat and a helpful pointer to sheet_describe. Every sentence earns its place.

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?

For a tool with two parameters and no output schema, the description is complete: it explains the tool's purpose, parameter semantics, behavioral nuances, and the prerequisite step when tab names are unknown. Nothing essential for correct invocation or interpretation is missing.

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 coverage is 50% and only the sheet parameter has a schema description. The tool description compensates by explaining range notation and limits ('A1:F20', 'max 60 rows × 26 columns') and by clarifying exact-tab-name requirements for sheet, including when it is mandatory. This adds substantial meaning beyond the schema.

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 states a specific verb and resource ('Read a rectangular range like A1:F20') and explains exactly what is returned ('values and formulas. Empty cells are omitted.'). It is clearly distinguishable from siblings like sheet_describe, sheet_find, and sheet_apply.

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?

It explicitly tells the agent when the sheet parameter is required ('when the workbook has more than one sheet'), warns about the consequence of omitting it, and names the alternative tool to call first ('Call sheet_describe first if you do not know the tab names'). This is exemplary guidance.

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