set_range_values

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

With no annotations provided, the description carries full burden but only states what the tool does, not behavioral traits. It doesn't disclose whether this overwrites existing data, requires file permissions, has file size limits, or what happens on success/failure. For a write operation with zero annotation coverage, this is insufficient.

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?

Single sentence, zero waste. Every word contributes to the core purpose. The description is appropriately sized and front-loaded with the essential action.

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 write operation with 4 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what happens to existing data in the range, error conditions, or return values. The schema covers parameter documentation well, but behavioral context is missing.

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%, providing good documentation for all 4 parameters. The description adds minimal value beyond the schema - it mentions '2次元配列のデータ' which aligns with the values parameter schema, but doesn't provide additional context about parameter interactions or edge cases.

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 ('設定します' - sets) and resource ('2次元配列のデータ' - 2D array data) with the target ('指定された範囲' - specified range). It distinguishes from siblings like set_cell_value (single cell) and get_range_values (read operation), but doesn't explicitly mention Excel/worksheet context which is only in the schema.

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?

No guidance on when to use this tool versus alternatives like set_cell_value (for single cells) or add_worksheet (for creating sheets). The description implies it's for writing 2D arrays to ranges, but doesn't provide explicit comparison or exclusion criteria.

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