spreadsheet_list_sheets

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

No annotations are provided, so the description carries full burden. It mentions 'including any bound dataset,' which gives some insight, but lacks details on authentication, error handling, or behavior (e.g., what happens if spreadsheet_id is invalid).

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?

A single, concise sentence that front-loads the core action. Every word is necessary, with no filler.

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 the tool's simplicity (one required param, output schema exists), the description is minimally adequate. It captures the main function but could mention consequences or prerequisites (e.g., spreadsheet must exist). The output schema likely provides details, but the description leaves some uncertainty.

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?

Only one parameter (spreadsheet_id) exists, and schema description coverage is 0%. The description adds no extra meaning beyond the schema title 'Spreadsheet Id.' While the name is self-explanatory, the description should provide context on valid values or expected format.

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 verb (List), the resource (sheets), and the scope (in a spreadsheet including bound datasets). It is unambiguous and distinguishes the tool from siblings like spreadsheet_update or spreadsheet_ui_url.

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?

No guidance on when to use this tool versus alternatives. Sibling tools like wdata_list_tables may overlap conceptually, but the description offers no differentiation or usage context.

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