list_all_sheets

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

Annotations already declare readOnlyHint=true, so the safe read behavior is covered. The description adds value by specifying that the tool returns row/column counts, which is not in the annotations. It also conveys a lightweight intent with 'Quick overview'.

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 short sentences, front-loaded with the primary action and adding a secondary benefit. Every word earns its place; no fluff, no redundancy.

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?

For a simple read-only list operation with a single obvious parameter and no output schema, the description is complete. It states what it does, what extra information is provided (row/column counts), and when to use it (before reading data). There are no significant gaps for the tool's simplicity.

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 has one parameter (filepath) with no description, and the tool description does not elaborate on it. Since schema coverage is 0%, the description carries the burden of explaining the parameter, but it only says 'workbook' without any details about file path format, required extensions, or how to reference the file.

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 action (List all sheets), the resource (in a workbook), and the specific detail (with row/column counts). This distinguishes it from sibling tools like list_tables or list_named_ranges, which target different resource types.

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 phrase 'Quick overview before reading data' provides clear contextual guidance on when to use this tool. However, it does not explicitly mention alternatives or exclusions, so it stops one step short of full guidance.

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