coda_delete_rows

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

Adds context beyond annotations: operation is irreversible, returns a requestId for async tracking. Annotations already mark destructiveHint=true, but description reinforces permanence and async nature.

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?

Three sentences with no wasted words: purpose, irreversibility, prerequisite, async return, and performance tip. Front-loaded with the core 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?

Covers all essential aspects: what it does, what it requires, what it returns, and why to use it over alternatives. For a 3-parameter destructive tool with async return, this is 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 provides complete descriptions for all three parameters (100% coverage). Description adds practical guidance for row_ids (use list_rows to get IDs), but doesn't add new semantics for doc_id or table_id_or_name. Still, the schema is sufficient.

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 action 'Delete multiple rows from a Coda table in a single call', distinguishing it from sibling coda_delete_row which deletes a single row. The verb and resource are specific.

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 instructs to 'List the rows first with coda_list_rows to get their IDs' and recommends this tool over coda_delete_row for performance and rate limit efficiency. Also states irreversibility, guiding appropriate usage.

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