Delete a person

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

Beyond the annotations' destructiveHint, the description adds concrete behavioral context: operator write opt-in is required, confirm must be true, and the action may notify recipients or change tenant data. It also states the HTTP verb and body expectations, which helps an agent anticipate side effects and authorization needs.

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 compact and front-loaded with 'Delete a person' before the endpoint and constraints. Each piece adds information, though the trailing reference and requirement section could use line breaks or punctuation for easier scanning.

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 call with two required parameters and no output schema, the description supplies the key invocation facts: how to target the person, what body/query expectations are, and what authorization and side-effect caveats exist. It does not detail error cases or how the operator opt-in is granted, but the annotations and schema cover the remainder.

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 endpoint template 'DELETE /api/xm/1/people/{personID}' clarifies the required path parameter, and 'Body fields: none' removes guesswork about a request body. The confirm requirement is reinforced, though query parameters are left generic by the schema's own description; this is reasonable for a delete operation.

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 opens with the explicit verb-object pair 'Delete a person' and grounds it in the exact HTTP endpoint. This clearly distinguishes it from sibling tools like get_a_person_by_id, create_a_person, and modify_a_person.

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 states necessary preconditions ('Requires operator write opt-in and confirm:true') and the resource to target, so the intended use is clear. However, it gives no explicit guidance about when to prefer deletion over alternatives such as modify_a_person, or any when-not-to-use scenarios.

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