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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals that formulas return their displayed values and that there is a 10,000-cell per-call limit, which are non-obvious behaviors. However, it does not mention error handling, authentication needs, or whether the operation is read-only (though 'read' implies it). The disclosed details add significant value beyond the schema.

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 concise sentences with no redundant phrasing. It front-loads the core action, then provides a usage tip, and finally a behavioral note. Every sentence serves a purpose, and the structure is efficient and clear.

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 no output schema, the description would benefit from describing the return format (e.g., a 2D array of values) and what happens when the limit is exceeded. It also omits error scenarios. However, for a straightforward read operation with a clear schema, the description covers the essential behavior (formula handling, cell cap) but leaves room for missing return-structure details.

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 75% (workbookId lacks a description). The description adds meaning by clarifying that 'range' is optional and by stating the cell limit, which directly affects range usage. It does not, however, provide additional context for workbookId or the output format, leaving some semantics to be inferred from the schema and tool name.

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 ('Read') and resource ('cell values from a worksheet'), which clearly conveys the tool's purpose. The name and context distinguish it from siblings like read_google_sheet_range, and the description adds a scoping detail ('Omit range to read whatever is occupied') that further clarifies the action.

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 gives a usage hint about omitting the range parameter, but it does not explicitly say when to use this tool versus alternatives like read_google_sheet_range or read_gdrive_file. It provides no exclusions or conditions, leaving the agent to infer the appropriate context from the tool name and schema.

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