spreadsheet_create

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

With no annotations, the description must compensate by describing behavior. It discloses the API limitation about destination folders, which is valuable. However, it does not mention what happens on duplicate names, required permissions, or the return value, leaving some behavioral gaps.

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 extremely concise with two sentences, no redundant information. The structure efficiently states the action followed by a critical note, earning maximum score.

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 the simplicity of the tool (one parameter, no output schema) and the context of sibling tools, the description provides essential info but lacks mention of the return value, error handling, or conflict behavior. Adequate but not comprehensive.

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 covers the single parameter with a clear description ('Spreadsheet name (without extension)'), and the description adds no further parameter details. Baseline of 3 is appropriate for 100% schema 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 verb 'Create' and the resource 'new empty Synology Spreadsheet (.osheet)', making the purpose unambiguous. It also differentiates from sibling tools by specifying it creates an empty file, not adding sheets or rows.

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 provides a helpful note about the API's lack of destination folder support and suggests using Drive tools to move the file, guiding when to use alternate tools. However, it does not explicitly state when not to use this tool or mention other prerequisites.

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