Update a database row

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

Beyond annotations (readOnlyHint=false, destructiveHint=false), description details partial patch behavior, null clearing, and position reordering. Adds context for kanban card movement. No contradiction.

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 sentences plus a note. Front-loaded with core action. Every sentence adds value. No fluff.

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?

Covers main usage: patch semantics, clearing, position, and kanban move. Mentions getting rowIds. Lacks error handling or return value description (no output schema). Adequate for a patch tool.

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%; description adds clarity to 'values' (maps name or id, only passed keys change, null clears) and 'position' (0-based reordering). Provides nuance beyond schema.

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 ('merge-patch ONE row'), the resource ('a Rootr DATABASE'), and identification method ('by rowId from rootr_read_database'). It distinguishes from siblings like rootr_add_row and rootr_read_database.

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?

Provides clear when-to-use: for updating a row with specific patch semantics. Includes special case for moving kanban cards. However, does not explicitly contrast with other update tools or state when not to use.

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