read_sheet_values

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

No annotations are provided, so the description carries the full burden. 'Reads values' correctly implies a non-mutating operation, and the return type is described. However, it does not disclose authorization prerequisites (e.g., prior OAuth via start_google_auth), potential errors, or rate limits. Basic but not rich.

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 concise docstring with a clear opening sentence, followed by structured Args and Returns sections. Every sentence adds value, and the front-loaded first sentence immediately conveys the core action.

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?

The tool is relatively simple (3 params, no nested objects), and an output schema exists, so return values are covered. The description provides necessary parameter details and return behavior. It lacks explicit mention of authentication prerequisites, but the user_google_email parameter hints at this. Overall, sufficiently complete.

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 0%, but the Args section explains every parameter, including the range format with an example ('Sheet1!A1:D10') and the default value ('A1:Z1000'). This fully compensates for the lack of schema descriptions.

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 starts with 'Reads values from a specific range in a Google Sheet,' which is a specific verb+resource pairing. It clearly distinguishes this read operation from sibling tools like modify_sheet_values or format_sheet_range.

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 implies usage when reading cell values from a range, but it does not explicitly state when to use this over alternatives or mention any exclusions. No alternatives are named, so the agent must infer from the 'Reads' verb.

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