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

No annotations are present, so the description carries the transparency burden. It clearly implies a read-only operation with 'Get' and discloses that the result includes all cell data in A1 notation. However, it does not mention potential errors, authorization requirements, or the response structure beyond the A1 notation detail.

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, focused sentence that leads with the action and resource, followed by a valuable detail about the data format. No redundant words or filler.

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?

With no output schema, the description partially explains the return by noting it includes all cell data in A1 notation, but leaves the exact response structure ambiguous. The tool is simple and parameters are fully documented, but missing guidance on when to use it and exact return shape reduces completeness.

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 input schema already documents both parameters with descriptions ('Tab ID' and 'Sheet (workbook) ID'). The description adds context by clarifying that the sheet is a workbook and the tab is the specific sheet within it, but does not add further parameter-level detail such as format or constraints.

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 uses the specific verb 'Get' and clearly specifies the resource: 'a single tab from a spreadsheet'. It adds detail about the return data ('all cell data in A1 notation') and includes terminology disambiguation ('sheet, excel, workbook') which helps differentiate it from sibling tools like get_sheet.

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. It does not mention that get_sheet might be for whole workbooks or that list_sheets is for discovery. No exclusions or alternative references are provided.

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