sheets_create

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

Annotations already indicate the operation is not read-only and not destructive, so the description does not need to restate that. The description adds a useful behavioral detail: it returns the new spreadsheet's id. It does not disclose side effects beyond creation, but for a simple create tool this is acceptable.

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 one sentence with no filler. Both the action and the result are front-loaded, and every word contributes to understanding the tool's behavior.

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 single-parameter create tool, the description is largely complete: it tells the agent what action to take and what will be returned. The only minor gaps are details like the format of the id or where the spreadsheet is stored, which are not critical for a basic invocation.

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, `title`, with no schema description and 0% coverage. The tool description does not explain what `title` means or how it relates to the new spreadsheet, leaving the agent to rely solely on the property name. This is a clear semantic 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?

The description states a specific action ('Create a new spreadsheet') and the return value ('return its id'). It clearly distinguishes sheets_create from sibling tools like sheets_read, sheets_write, sheets_append, and sheets_get by signaling the create operation.

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?

Usage is implied by the verb 'Create' — an agent can infer this is the tool to use when a new spreadsheet is needed. However, the description gives no explicit when-to-use guidance or exclusions naming alternatives, so it lacks direct comparison with sibling creation tools.

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