pls_delete_building

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

Annotations already declare destructiveHint=true. The description adds that deletion is irreversible and requires a confirmation parameter, reinforcing the destructive nature. However, it doesn't mention side effects on related entities or error conditions.

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?

Concise, well-structured with emoji, clear sections for purpose, parameters, return, and tip. Every sentence adds value; no redundancy.

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?

Moderate completeness: the return format is described, but error handling, relationship between 'id' and 'ids' parameters (both in schema but only 'ids' mentioned), and clarification of vague note are missing. No output schema exists, so description could do more.

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 lists confirm and ids but also adds a vague note about passing fields according to entity type. It does not significantly enhance understanding beyond the schema's existing parameter descriptions.

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 tool deletes a building entity ('删除楼栋实体'), with specific verb+resource. It distinguishes from other pls_delete_* tools by naming 'building', but lacks explicit differentiation beyond entity type.

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 on when to use this tool versus alternatives (e.g., other delete tools). No prerequisites, context, or scenarios provided. Only a warning about irreversibility, which is cautionary but not usage advice.

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