get_sheet_data

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds that output is JSON records and that results are optionally column-limited and paged, but it does not disclose row caps, error behavior, or return structure beyond the basic format.

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, well-formed sentence that front-loads the core action and result. Every word contributes to the stated capability with no filler or repetition.

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 rich schema descriptions and comprehensive read-only annotations, the description is nearly sufficient for correct invocation. However, because there is no output schema, it could say more about the returned JSON record shape or header handling, making it slightly incomplete for an agent needing return-value expectations.

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 100%, so all six parameters are already documented, including path, limit, sheet, offset, columns, and header_row. The description merely echoes the optional column limitation and paging without adding syntax, defaults, or edge-case 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 ('Return') and resource ('a sheet's rows as JSON records') with scope modifiers for columns and paging. It is clear what the tool does, but it does not explicitly differentiate itself from siblings like read_spreadsheet or get_formulas.

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 offers no guidance on when to use this tool versus alternatives such as read_spreadsheet, get_summary_stats, or search. It only describes capability, leaving the agent to infer appropriate contexts and exclusions.

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