Delete Rows from SiYuan Database

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

The description merely restates the tool's name and schema; it does not disclose that deletion is permanent, any side effects, or required permissions. With no annotations, the full burden falls on the description, which fails to add behavioral 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 short sentence, easy to scan, with no filler. However, it is so terse that it borders on under-specification rather than conciseness.

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 the destructive nature and lack of annotations or output schema, the description is inadequate. It does not mention reversibility, error handling, or what happens after deletion. It would not fully prepare an agent to anticipate the operation's effects.

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 input schema already provides complete descriptions for both avID and rowIDs (100% coverage), so the baseline is 3. The description adds no additional parameter context, such as how to obtain IDs or constraints.

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 (delete) and target (rows from a database), which is specific enough to differentiate from sibling tools like av_addRow and av_updateRow. However, it omits the SiYuan/Attribute View context that appears in the title, making it slightly generic.

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?

No guidance is provided about when to use this tool versus alternatives. There is no mention of prerequisites, consequences, or situations where one might prefer a different tool.

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