pls_delete_area_rule

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. Description adds crucial context: '删除不可撤销！' (deletion irreversible) and the confirm parameter as a safety mechanism, along with return format. 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?

Description is concise and front-loaded with purpose. Parameter list is bullet-style but clear. Could be slightly more streamlined, but overall efficient.

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 delete tool with full schema coverage and annotations, description covers purpose, required params, return format, and irreversibility. No output schema exists, so return format is described. No mention of relationship with other area rule tools, but not essential for a delete operation.

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 baseline is 3. The description repeats parameter info from schema (e.g., confirm must be '确认', ids list) without adding new meaning beyond what schema provides.

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 title and description explicitly state '删除区域规则实体' (delete area rule entity), clearly identifying the action and resource. It distinguishes itself from sibling delete tools by specifying 'area rule'.

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?

Description explains required parameters (confirm, ids) and that deletion is irreversible, but does not provide explicit when-to-use or when-not-to-use guidance compared to alternatives. The context is clear for its specific use case.

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