delete_questions

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

With no annotations, the description fully discloses behavior: dry_run returns a list without modifying data, confirm triggers backup and deletion of all related rows, logs audit, lists blocking conditions, and requires string IDs. It also states the deletion is irreversible.

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 dense with information but uses symbols and Chinese punctuation. It is front-loaded with key points but could be more structured. Still, every sentence adds value.

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 complexity (4 parameters, output schema present), the description covers deletion behavior, conditions, limits, irreversibility, backup, and audit. It is sufficiently complete 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?

Schema description coverage is 0%, so the description must compensate. It explains confirm (default false), mentions backup_path, and implies question_ids as targets. However, reason and backup_dir parameters are not explicitly explained, leaving some ambiguity.

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 states '安全删题（只能删散题）' meaning safe deletion of standalone questions, clearly identifying the verb and resource. It distinguishes from sibling tools by specifying the scope (only standalone questions) and no other deletion tool exists among siblings.

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 explicit when-to-use (deleting standalone questions) and when-not-to-use (blocked by various conditions). Explains dry_run mode for preview vs confirm for actual deletion, and mentions single limit of 500. Also notes that deletion is irreversible and recommends dry_run first.

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