drive_sheets_info

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

With no annotations, the description carries the full disclosure burden and does so well: it explains the underlying spreadsheets.get fields mask, why the call stays cheap regardless of workbook size, that no cell values are ever fetched, and that output is YAML. That is meaningful behavior beyond restating the name.

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?

Front-loaded and dense with no filler sentences, but the long em-dash parenthetical about the fields mask makes the first sentence run-on and slightly harder to parse than necessary. Every clause still earns its place.

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?

No output schema exists, yet the description names the returned fields (title, per-tab dimensions and hidden flag) and the output format (YAML), so an agent knows the shape of the result. Nothing needed to invoke this low-risk read tool correctly is missing.

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% with only two params, so the schema already documents spreadsheet_id and the account resolution behavior thoroughly. The description adds nothing about either parameter, which is the expected baseline when structured data does the work.

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?

States a specific verb+resource (show a spreadsheet's title and its sheet/tab metadata) and enumerates exactly what is returned (dimensions, hidden flag per tab) and what is not (cell data). It is clearly distinguishable from the sibling drive_sheets_read and drive_docs_info without opening any schema.

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?

Names the alternative tool explicitly: 'Use drive_sheets_read for actual cell values,' which is the precise routing rule an agent needs when choosing between the two. Read-only is declared, so the safety context for selection is also covered.

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