table_copy_row

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state whether the action mutates the table, whether it has side effects like marking a row, how the copied row is stored, or what happens if there is no current row. The one-line description offers little behavioral context beyond the literal action.

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 one short sentence with no filler and is easy to parse. It loses points only because the brevity sacrifices operational clarity that the dimensions above need.

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 that there are no annotations and no output schema, the description is insufficient for a reliable invocation. It does not explain the effect of copying, how the result is used, what input parameters are needed, or any error/edge-case behavior.

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 0%, and the description does not explain any of the three parameters (name, title, session_id). While the parameters have defaults and are optional, an agent cannot determine from the description how these relate to identifying the form table or session.

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 states a specific verb ('Copy') and resource ('current row in a form table'), and the wording distinguishes it from sibling row operations such as table_add_row, table_move_row, and table_delete_row. However, it does not clarify what 'copy' means operationally, such as whether it copies to the clipboard or an internal buffer.

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 like table_add_row, table_set_row_values, or table_find_row. There is no mention of prerequisites, such as having a current row selected, or behavior in edge cases like an empty table.

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