spreadsheet_list

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

Without annotations, the description carries the full burden. It only says 'List', implying read-only, but no behavioral details such as authorization needs, performance impact, or side effects. The description lacks transparency about the nature of the operation.

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 single clear sentence, very concise and front-loaded. It wastes no words but could be enhanced with minimal additional structure (e.g., mentioning pagination).

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 annotations and no output schema, the description is incomplete. It does not explain the return format, pagination behavior (limit/offset), or folder_path syntax. Essential context for a list tool is missing.

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?

Schema description coverage is only 33% (only 'folder_path' has a description). The tool's description adds no additional meaning for parameters 'limit' and 'offset', which are undocumented in the schema. It fails to compensate for the low coverage.

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 tool lists Synology Spreadsheet (.osheet) files in a Drive folder, using a specific verb 'List' and resource 'Synology Spreadsheet files'. It distinguishes from sibling tools like 'drive_list_files' (all files) and 'spreadsheet_read_sheet' (reads content).

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 provided on when to use this tool versus alternatives. There is no mention of when not to use it or comparison to similar tools like 'drive_list_files' or 'spreadsheet_get_info'.

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