duplicate_table_row

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

Discloses deep-copy and insertion behavior, but with no annotations, it lacks details on side effects (e.g., impact on merged cells, indexes) and does not mention any restrictions or prerequisites.

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?

Extremely concise with a one-line summary followed by clearly separated args and returns. No unnecessary words, well-structured.

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 two-parameter tool with a simple output schema, the description is adequate but misses potential edge cases (e.g., behavior with merged cells, indexing shift after insertion). More detail would improve completeness.

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?

Description explains both parameters as 0-based indices, adding meaning beyond the schema which only gives names and types. The schema's description coverage is 0%, so the description compensates well.

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 it deep-copies a table row and inserts the copy immediately after. This distinguishes it from siblings like add_table_row, delete_table_row, copy_table.

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?

Implied usage is clear, but no explicit guidance on when to use vs alternatives (e.g., copy_table, add_table_row) or conditions when not to use.

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