delete_person

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

The description adds 'This action cannot be undone', which provides context beyond annotations (destructiveHint=true, idempotentHint=true). It reinforces the irreversible nature, which is valuable for an agent. No contradiction with annotations.

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 only two sentences, front-loaded with the core purpose. Every word is meaningful: 'Permanently delete a person from Huly' is precise, and the second sentence adds crucial permanence info. No redundancy or fluff.

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 simple delete operation with no output schema, the description adequately captures the action and its irreversibility. It does not explain error behavior or permissions, but given the low complexity, this is sufficient. Slightly incomplete for an agent to handle edge cases.

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 defines personId with description 'a string that will be trimmed'. The tool description adds no further clarification about the parameter (e.g., its format or purpose). Since schema coverage is 100%, baseline is 3; the description does not enhance understanding.

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 'Permanently delete a person from Huly', specifying the verb 'delete' and the resource 'person'. Among siblings, there are distinct delete tools for other entities and a create_person tool, so this tool is well-differentiated.

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 implies usage when permanent removal of a person is intended, but it does not explicitly discuss when to use this tool vs alternatives (e.g., preview_deletion or soft-delete options). No guidance on prerequisites or conditions.

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