Write cells into a Rootr spreadsheet sheet (preferred way to fill in data)

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

Annotations indicate non-read-only and non-destructive, but description adds crucial details: sparse patch (only touches keys sent), setting null clears cells, and formulas are recalculated server-side. No 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?

Description is appropriately sized (~100 words) and front-loaded with key purpose. Could be slightly more concise but every sentence adds value.

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?

Given no output schema, description covers preconditions (read first), behavior (sparse patch, null clearing), and usage guidance. Comprehensive for a patching tool.

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 coverage is 100%, but description adds value by explaining A1-style addressing, the sparse map format with examples, and the null clearing behavior, which enriches understanding beyond schema.

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?

Description clearly states 'Sparse-patch cells of ONE sheet' with specific verb and resource, and distinguishes from sibling 'rootr_update_spreadsheet' by stating preference when only editing cell values/formulas.

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?

Explicitly says 'PREFER this over rootr_update_spreadsheet when you are only filling in / editing cell values or formulas' and advises reading the sheet first via 'rootr_read_spreadsheet' to know dimensions and content.

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