Convert spreadsheets

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

Annotations declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, so the agent already knows this writes files without being flagged destructive. The description adds that inputs may be one file, a list, or a folder, but says nothing about overwrite semantics, whether output files are preserved by default, or side effects on the source workbook.

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 sentence that goes inputs → outputs → option semantics, with nothing wasted. The nested parentheticals make it dense but every clause carries information an agent needs.

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 9-parameter, mostly-optional conversion tool with no output schema, the description covers the essentials an agent needs to invoke it: accepted inputs, target formats, and the one non-obvious output-shaping flag. Remaining gaps (suffix, output pathing, overwrite) are defaults the schema surfaces.

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?

At 56% schema coverage, several parameters (suffix, output_path, output_dir, overwrite) are undocumented in both places. The description does add real meaning for the plurality of the input ('one, a list or a folder' maps to input_path/input_paths/input_dir) and for the all_sheets output naming, but only partially compensates for the coverage gap.

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 (convert) and resource (workbooks) and enumerates both the accepted input formats and the producible output formats, which no sibling (create/edit/read_workbook) does. An agent can pick this tool over its siblings 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?

The format matrix effectively delimits when this tool applies and the parenthetical explains the all_sheets decision point for csv/tsv/pdf. It stops short of explicit alternatives or when-not-to-use guidance (e.g. use read_workbook to merely inspect), so it is clear context rather than full routing.

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