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

Since no annotations are provided, the description carries the full burden of disclosing behavior, and it does so thoroughly. It covers atomicity ('ALL-OR-NOTHING', rollback, safe resend), batch limits ('Up to 500 rows per call'), single-surface targeting, the auto_create_columns schema-extension behavior, and the return shape.

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 dense but every sentence earns its place: purpose, when to use, payload shape, limits, atomicity, target surface, column behavior, and return value are all covered without redundancy. It is front-loaded with the core action and differentiator.

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 4-parameter tool with no annotation coverage and no output schema, the description provides everything needed to invoke it correctly: required vs optional parameters, batch constraints, rollback behavior, schema-extension side effect, and returned fields. No critical gap remains for the agent to infer.

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?

Even though the schema already documents all four parameters, the description adds meaning beyond the structured fields: it clarifies the exact rows payload shape as `{ data: {...} }` maps, states the batch limit, explains the all-or-nothing failure semantics, and specifies that auto_create_columns performs 'one schema extension'. This materially helps an agent formulate correct calls.

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 opens with a specific action and resource: 'Append many rows to a workspace's table surface in ONE call.' It also explicitly identifies itself as 'the bulk version of create_row', which distinguishes it from the create_row sibling and makes its purpose unambiguous.

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?

It gives direct usage guidance: 'Use this instead of looping create_row when ingesting more than a few rows (lower latency + token cost).' This names the alternative and the exact condition for choosing this tool, leaving no ambiguity about when it should be used.

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