Delete a database row

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

Annotations already set destructiveHint=true, but the description adds valuable context: it deletes exactly one row, and any linked page is moved to the trash (not permanently deleted). This goes beyond the annotation by explaining the side effect, aiding the agent in understanding the tool's behavior.

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 with no wasted words. The first sentence states the core action and a key side effect; the second provides a critical safety instruction. It is front-loaded and every sentence 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?

For a simple delete operation, the description covers the essential: what is deleted (one row), how to identify it (rowId, databaseId), and what happens to linked content (moved to trash). It also includes a usage caution. No output schema is needed for a delete tool, so the description is 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 parameters are already well-described in the schema. The description adds no additional semantic detail about the parameters beyond mentioning rowId and database by name. The side effect about linked pages is behavioral, not parameter-specific. This meets the baseline of 3.

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 uses a specific verb 'Delete' and identifies the resource as 'ONE row of a Rootr DATABASE'. It distinguishes from siblings like rootr_add_row or rootr_update_row by specifying the action is deletion and mentions the side effect of moving linked pages to trash, which is unique.

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 explicitly advises 'Verify the row via rootr_read_database first — do not guess rowIds', providing clear when-to-use guidance and a caution. While it does not explicitly list when not to use, the instruction implies the tool should only be used after verification, and the sibling set makes the distinction clear.

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