update_rows

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

Annotations indicate it is not read-only and not destructive. The description adds the behavioral safety constraint that WHERE is mandatory to prevent accidental full-table updates, which is valuable beyond annotations. However, it does not disclose return behavior or transaction semantics, so it adds some but not extensive context.

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 a single, tightly crafted sentence that conveys the operation type, required clauses, safety note, and optional schema. It is front-loaded, with no redundant words, making it highly concise and 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 tool with 4 parameters and no output schema, the description covers the core semantics: table, set, where, schema, and the safety rationale. It lacks details on return values or error conditions, but it is sufficient for an agent to select and invoke the tool correctly in most scenarios.

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?

With 75% schema coverage, the description enriches parameter meaning by explaining SET and WHERE and emphasizing that WHERE is required for safety—this is not present in the schema. It also clarifies the default schema behavior, adding useful semantics beyond the raw property definitions.

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 it performs a parameterized UPDATE on a specified table, with SET and WHERE clauses. It distinguishes from siblings by explicitly naming it as an update operation and highlights the mandatory WHERE to prevent full-table errors, making its purpose specific and actionable.

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 provides a safety guideline (WHERE required to avoid full-table update) but does not explicitly contrast with alternatives like insert_rows, delete_rows, or execute. The context implies usage for modifying existing rows, but there is no explicit 'when not to use' or alternative selection guidance.

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