read_full_sheet

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

Discloses reading entire tab, writing to local CSV, and returning path/preview. Annotations indicate non-read-only and non-destructive, which aligns. Missing details on error conditions or file overwrite behavior, but overall transparent.

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?

Two concise paragraphs with no fluff. First sentence summarizes action, details follow. Every sentence provides value.

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?

Handles all key aspects: input (item, tab, dest_path), output (rows/cols and preview), and side effect (file write). No output schema, so description suffices. Lacks error handling details, but complete for typical use.

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?

Explanation covers item (URL/ID), tab (default first), and dest_path (resolved in sandbox), but does not mention the 'values' parameter (default UNFORMATTED) or its options. Schema description coverage is 0%, so description partially compensates.

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 tool reads an entire sheet tab, saves to CSV, and returns path + preview. It distinguishes from siblings by comparing with read_sheet and noting it provides complete data without flooding context.

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?

Explicitly recommends using this tool over read_sheet when full data is needed, providing clear when-to-use guidance. No alternative is mentioned for other scenarios, but the comparison is sufficient.

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