Query Update Records

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

Annotations already declare destructiveHint=true, but the description adds critical behavioral context: the dry-run mode, confirm=false default behavior, and the warning that confirm=true modifies records. This goes beyond structured annotations by disclosing the safety mechanism and the irreversible nature of the operation.

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 tight paragraphs, no wasted words. The main action is stated first, followed by the critical safety information. The important warning is bolded for emphasis, making it effective and front-loaded.

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 destructive tool with no output schema, the description covers the essential workflow: dry-run first, then execute. It hints at the return value (match count) and warns about modifications. It omits details like limit behavior or instance fallback, but those are fully documented in the schema, so the description is sufficiently complete.

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%, so the baseline is 3. The description adds value by explaining the confirm parameter's role in dry-run vs. execution, which is not fully captured by the schema's field description. It also clarifies the 'update them all' semantics for limit, though not in detail.

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 'Find records matching an encoded query and update them all with the specified data,' which clearly states the verb (update), resource (records matching a query), and scope (all matches). It also distinguishes itself from siblings like query_table (read-only) and query_delete_records (delete) by focusing on updating.

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 explicit guidance on when to use the tool: 'Always run a dry-run first' and explains the confirm flag's role in controlling execution. It does not explicitly name alternatives or exclusions, but the dry-run-first instruction strongly implies the safe usage pattern for this mutation tool.

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