read_sheet

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

No annotations are provided, so the description carries the full behavioral burden. It does indicate that the tool reads data (implying non-destructive), but it fails to disclose expected return format, default row limits, pagination behavior, or any side effects. The word 'read' is the only behavioral signal, and it lacks the contextual depth needed for safe autonomous invocation.

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 concise sentence with no redundant wording. It is front-loaded with the verb and resource, but it may be too terse to convey full utility. Still, it earns its place with a clear subject and method.

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 and only two parameters, the description is too minimal to be fully contextual. It does not explain what 'data' means (all rows? specific columns?), how the 'limit' parameter affects behavior, or what the response looks like. These gaps leave an agent uncertain about the tool's behavior beyond the basic read operation.

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 provides descriptions for both parameters (endpoint and limit), achieving 100% schema coverage. The description itself does not add semantic meaning about parameters beyond that, so per the rubric, the baseline score of 3 is appropriate.

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 'read' and identifies the resource as 'a Google Sheet' via 'SheetsDB'. This clearly distinguishes it from sibling write/delete tools like update_row and delete_rows, and from get_keys, which deals with keys rather than sheet data.

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 explicit guidance on when to use this tool versus alternatives. It simply states what it does, without mentioning any exclusions, prerequisites, or preference over sibling tools. The verb 'read' implies a read operation, but there is no direct comparison or contrast.

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