read_sheet_data

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 states the tool reads data but doesn't mention any behavioral traits such as permissions required, rate limits, error handling, or output format. This is a significant gap for a tool that interacts with external resources like Google Sheets.

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, efficient sentence that directly states the tool's purpose and parameters. It is front-loaded with essential information and contains no redundant or unnecessary details, making it highly concise and well-structured.

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 complexity of interacting with Google Sheets and the lack of annotations and output schema, the description is incomplete. It doesn't cover behavioral aspects, usage guidelines, or output details, leaving gaps that could hinder an agent's ability to use the tool effectively in context with its siblings.

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 the schema already documents both parameters thoroughly. The description adds minimal value beyond restating the parameters (spreadsheet ID and range), without providing additional context like format examples or usage tips. Baseline 3 is appropriate as the schema does the heavy lifting.

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 data from') and resource ('a Google Sheet'), specifying the required inputs (spreadsheet ID and range). It distinguishes from siblings like 'get_sheet_metadata' by focusing on data extraction, but doesn't explicitly differentiate from 'get_range_data' or 'search_sheet_data', which may have overlapping functionality.

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 is provided on when to use this tool versus alternatives like 'get_range_data' or 'search_sheet_data'. The description lacks context about use cases, prerequisites, or exclusions, leaving the agent to infer usage based on tool names alone.

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