delete_reservation_by_name

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

With no annotations provided, the description carries full burden. It states this is a deletion operation (destructive), but doesn't disclose behavioral traits like whether deletion is permanent/reversible, what permissions are needed, error handling (e.g., if name not found), or side effects. For a destructive tool with zero annotation coverage, this is insufficient.

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, efficient Chinese sentence that directly states the tool's purpose without any fluff. It's appropriately sized and front-loaded with the core functionality.

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 destructive deletion tool with no annotations and no output schema, the description is incomplete. It doesn't explain what happens on success/failure, return values, or important behavioral context. Given the complexity of a delete operation and lack of structured coverage, more information is needed.

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 100%, with the single parameter 'name' clearly documented in the schema as '预约人姓名' (reservation person's name). The description adds no additional parameter semantics beyond what the schema already provides, so baseline 3 is appropriate.

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 ('删除' meaning delete) and resource ('预约记录' meaning reservation records) with a specific criterion ('根据预约人姓名' meaning by reservation person's name). It distinguishes from sibling 'delete_reservation' which likely deletes by ID, but doesn't explicitly differentiate from 'delete_reservation_by_mobile' which uses mobile number instead of name.

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 like 'delete_reservation_by_mobile' or 'delete_reservation'. The description implies usage when you have a name to delete by, but doesn't specify prerequisites, error conditions, or comparison with other deletion methods.

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