pls_delete_person

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

Annotations already indicate destructiveHint=true. The description adds value by stating '删除不可撤销' (deletion irreversible) and emphasizing the confirm parameter, which clarifies the need for explicit confirmation. However, it does not disclose potential side effects like cascade deletions or permission requirements.

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 moderately concise but includes decorative elements like emojis and brackets (e.g., 【🔧 管理】) that add noise. The parameter list is clear, but the structure could be improved by removing unnecessary formatting. It earns a middle score due to being somewhat efficient but not optimally structured.

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 (confirm parameter, irreversible) and 8 parameters, the description lacks details on return values (only mentions success/false with entity and action) and error handling. No prerequisites or authorization info is provided. The tool could be better contextualized for an agent to use reliably.

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 has 100% description coverage for parameters. The description reiterates key parameters (confirm, ids) but adds minimal new semantic information beyond '根据实体类型传入对应字段' (pass corresponding fields based on entity type). Baseline 3 is appropriate as schema already explains parameters well.

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 explicitly states '删除人员实体' (delete person entity), which clearly identifies the action and resource. The tool name also indicates deletion of a person. Among sibling tools, there are many delete operations, but the description differentiates by specifying 'person' entity.

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 does not provide when to use this tool versus alternative deletion tools like pls_delete_tag or pls_delete_car. No guidance on prerequisites or contraindications is given. The only contextual hint is the confirm parameter requirement, which is a compliance measure rather than usage context.

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