sheets_insert_date

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

Annotations already declare idempotentHint=true and destructiveHint=false, covering safety and repeatability. The description adds behavioral context about automatic detection and locale support, but does not disclose what happens to existing cell contents or how formatting is applied. This adds some value beyond annotations without contradiction.

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, concise sentence that front-loads the primary action and key differentiators. Every word earns its place with no fluff.

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 tool with 6 parameters and no output schema, the description plus rich schema provides adequate context for basic use. It does not clarify multi-cell range behavior or return values, but the tool's purpose is simple and the schema covers all parameters. Given moderate complexity, this is reasonably complete.

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 100%, so all parameters (date, range, format, autoDetect, useEUFormat, spreadsheetId) are documented. The description's mention of 'locale support' and 'automatic detection' loosely aligns with format and autoDetect params, but it adds no new meaning beyond the schema. Baseline 3 is appropriate.

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's function: 'Insert properly formatted dates in Google Sheets' with specific features like locale support and automatic detection. This verb+resource+feature structure distinguishes it from sibling tools like sheets_update_values or sheets_format_cells.

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 conveys the tool's niche—handling date insertion with locale awareness—but does not explicitly name alternative tools or when not to use them. The context is clear enough for an agent to select it for date-specific tasks, though it lacks explicit exclusions.

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