spreadsheet_export

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

No annotations are provided, so the description must disclose behavior. It states it returns base64 content and implies a download-like operation, but does not mention authentication requirements, rate limits, or side effects (though export is likely read-only). The information is adequate but not comprehensive.

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 two sentences long, immediately stating the core purpose and key parameter distinction. Every phrase is necessary; no redundant information.

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 no output schema, the description explains the return format (base64 content). It does not cover error cases or performance considerations, but for a straightforward export tool, the completeness is sufficient. Sibling tools are primarily spreadsheet editors and readers, making the purpose clear.

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?

Input schema coverage is 100%, providing a baseline of 3. The description adds value by explaining the override behavior of file_id over name, the disambiguation role of path, and the default sheet for CSV export, which is not fully captured in schema descriptions.

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 specifies the action (export), resource (Synology Spreadsheet), target formats (xlsx/csv), and output (base64 content). It distinguishes from sibling tools like spreadsheet_read_sheet by focusing on full file export.

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 description mentions providing file_id or name, and the path for disambiguation, but lacks explicit guidance on when to use this tool versus alternatives like spreadsheet_read_sheet or calendar export tools. The sheet_name detail is helpful for CSV.

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