rm_delete_client

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

Annotations already declare destructiveHint=true, and the description reinforces this with 'Destructive' while adding the crucial safety requirement that confirm=True is required. This goes beyond the structured data and gives the agent a clear guardrail.

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?

One compact sentence with no filler. The core action is front-loaded, and the critical confirmation requirement is included as a parenthetical that earns its place.

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 straightforward destructive delete with annotations covering read-only/destructive status and an output schema present, the description is nearly complete. It could mention cascading effects on related client contacts, but that is not essential for calling the tool correctly.

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 0%, so the description must compensate. It adds real value for the confirm parameter by explicitly requiring confirm=True. The client_id parameter's purpose is inferable from 'client record', but no additional format or edge-case guidance is provided.

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 starts with a specific verb and resource: 'Delete a client record'. This clearly distinguishes it from sibling tools like rm_delete_client_contact or rm_update_client, and the destructive nature is stated up front.

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 use when a client record needs to be deleted, but it does not explicitly state when to avoid this tool or mention alternatives such as soft-delete or deleting related client contacts first. The guidance is adequate but relies on inference.

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