tracecat_insert_row

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

With no annotations, the description caries full burden but only mentions a data constraint. It omits side effects, return behavior, error handling, or idempotency.

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?

Two straightforward sentences with no extraneous information; efficiently communicates the core information.

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?

Adequate for a simple insert tool but lacks details on return values, error conditions, or dependencies, leaving some uncertainty.

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% and the description largely repeats the schema's note about matching column names, adding no significant new meaning beyond that.

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 ('insert a new row') and the resource ('into a table'), distinguishing it from siblings like tracecat_batch_insert_rows, tracecat_update_row, etc.

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 implies usage for inserting a single row but lacks explicit guidance on when to use vs. batch insert or prerequisites like table existence.

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