workspace_update_sheet

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

The description clarifies the overwrite behavior and uses 'PUT' to indicate the method. Annotations already provide idempotentHint and openWorldHint, so the description adds context on the destructive nature of overwriting.

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, well-structured sentence that clearly states the action, resource, and method. It is concise and front-loaded with the verb and resource.

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 4 parameters fully described in the schema, no output schema, and clear sibling distinctions, the description is adequate. It could mention response behavior but is largely 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?

All parameters are described in the schema with 100% coverage. The description adds no new semantic information beyond what the schema already provides, maintaining a baseline score.

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 updates cell values in a Google Sheets range, specifies it uses PUT (overwrites completely), and distinguishes itself from the sibling tool 'workspace_append_sheet' which implies appending rather than replacing.

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 'overwrites the range completely' and 'PUT', hinting at full replacement. While it doesn't explicitly state when not to use it, the presence of sibling 'workspace_append_sheet' provides context for alternative usage.

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