sheets_get_sheet_structure

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

Description explains it's a lightweight tool with a single API call and minimal field mask, implying efficiency. No annotations provided, but the description adequately covers behavioral traits like read-only nature and speed, though it doesn't mention error cases.

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?

Description is concise with front-loaded purpose and a clear list of returns. No unnecessary words, though could be broken into bullet points for clarity.

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 no output schema, description lists return fields but lacks format details (e.g., units for column widths). It sufficiently explains purpose and distinguishes from one sibling, but could mention more alternatives.

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 100% with descriptions for both parameters. The description adds minimal extra meaning beyond the schema (e.g., 'Name of the sheet (tab) to inspect' is similar to schema). Baseline score 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?

Description clearly states it returns structural/dimensional metadata only, not per-cell data. It lists specific return fields and distinguishes from sibling tool sheets_get_full_sheet_snapshot.

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 says 'Use this instead of sheets_get_full_sheet_snapshot when per-cell formatting is not needed' and notes it's faster and cheaper, providing clear when-to-use guidance.

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