get_spreadsheet_structure

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

No annotations are provided, so the description carries the full burden. The description misrepresents the tool's behavior by describing print scaling operations that do not match the tool's name or schema. It does not disclose what the tool actually returns, nor does it mention any constraints or side effects. This is deeply misleading.

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?

The description is a verbose paragraph that is entirely irrelevant to the tool's actual function. It is not front-loaded with a clear purpose, and every sentence adds confusion rather than clarity. It could be replaced with a single accurate sentence.

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?

Even though an output schema exists, the description fails to provide the most basic context about what the tool does. It describes printing and scaling, which is unrelated to retrieving spreadsheet structure. The tool is completely misrepresented, leaving the agent with no accurate information about its function.

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 schema has one parameter (spreadsheet_b64string) with no description. The description adds no value for this parameter and instead references 'scaling mode' parameters that do not exist in the schema. This actively confuses the agent about what inputs are valid.

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 focuses on print scaling when converting spreadsheets, but the tool name is 'get_spreadsheet_structure', which implies retrieving structure. This is a complete mismatch. The description does not state the actual purpose of getting spreadsheet structure, and it fails to distinguish from siblings like get_structure_with_file_token.

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 is given on when to use this tool versus alternatives. The description talks about printing and scaling, which overlaps with sibling tools like save_spreadsheet_as_with_scaling_mode. It does not mention that this tool is for reading/retrieving structure, nor does it provide context or exclusions.

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