Update database record

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 discloses key behaviors: shallow-merge by default, replace option, and that the id always stays fixed. This is strong transparency for a CRUD tool, though it could mention error states or authorization needs.

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 two sentences, zero filler. The first sentence states the core purpose, and the second adds critical behavior details. Every word earns its place.

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?

Given no output schema and moderate complexity (4 params, one with enum), the description covers merge behavior and id fixity well. It could briefly mention what happens on success or failure, but overall sufficient for correct tool usage.

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?

The schema coverage is 100%, so the schema already documents parameters well. The description adds value by explaining the effect of merge and the id fixity, but these are already implied by the schema. Baseline 3 is appropriate.

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 tool name 'update_record' and description clearly state it updates a database record, with specific verbs 'update' and semantic distinction from siblings like 'create_record' and 'search_records'. The description adds the merge behavior, further clarifying purpose.

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 explains when to use merge=true vs false ('shallow-merged' vs 'replace'), providing clear context. However, it does not explicitly state when not to use this tool or compare with alternative tools (e.g., when to use update vs create), which would make it a 5.

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