add_data_table_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. It explicitly states 'MUTATES data' and instructs user confirmation, plus explains the '$field-uuid' workaround. This is strong behavioral disclosure beyond the bare 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?

Three concise sentences: the action, parameter guidance, and mutation warning. Each sentence delivers distinct value with no redundancy.

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 2-param tool with no output schema, the description covers operation, parameter origins, and mutation warning. It omits any mention of success/error responses, but the absence of an output schema makes that less critical. The need for an existing table is implied via list_data_tables.

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 only lists types (string, string). Description adds essential semantics: table_id is a UUID from list_data_tables, document_json is a JSON object with field_name/value mapping, and the special '$field-uuid' key. Fully compensates for the 0% schema coverage.

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?

States 'Add a record to a Data Table' with a specific verb and resource, and even identifies the record API. References list_data_tables for table_id, distinguishing it from other table operations like update or delete.

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?

Provides clear context: table_id comes from list_data_tables, document_json is a JSON object, and the user should be confirmed before mutating data. However, it does not explicitly name alternatives or say when not to use this tool.

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