sheets_clear

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It does not mention side effects such as whether formatting is preserved, whether the action is reversible, or any permission requirements. The statement 'Clear values' is minimal and does not add context beyond the tool name.

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 sentence with no unnecessary words. It is front-loaded with the key verb and object, making it highly concise while still conveying the essential purpose.

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?

The tool is simple (2 params, straightforward action), and an output schema exists, so return values need not be described. However, the description lacks essential context such as range format and behavioral caveats, which are critical for correct invocation. It is minimally complete but leaves clear gaps.

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 has zero description coverage for parameters, and the description does not compensate. It mentions 'range' but does not explain the expected format (e.g., 'Sheet1!A1:B2' or 'A1:B2'), and it only alludes to 'Google Sheet' for spreadsheet_id. The description adds little meaning over the parameter names alone.

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 'Clear values from a range in a Google Sheet' uses a specific verb ('clear') and resource ('range in a Google Sheet'), making it distinct from sibling tools like sheets_write, sheets_append, and sheets_read. It unambiguously states the tool's core 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?

The description provides no guidance on when to use this tool versus alternatives (e.g., sheets_write, sheets_append, or clearing an entire sheet). It does not mention exclusions, prerequisites, or recommended scenarios, leaving the agent to infer usage solely from the name and description.

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