Users: Delete a User

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

Annotations already declare destructiveHint, idempotentHint and openWorldHint, so the permanence statement is partly redundant. The description does add new context the annotations lack: the required auth header ('api-access-token') and the platform endpoint path. It stops short of describing cascade effects or behavior when the ID does not exist.

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 operation, endpoint, auth and destructive warning are front-loaded and efficient. However, the trailing sentence about writing text values in Persian is irrelevant to a delete-by-ID call that sends no text, so it is wasted space rather than earning 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 one-parameter destructive tool with full schema coverage and full annotations but no output schema, the description covers the essentials: endpoint, auth, and permanence. It omits error/not-found behavior and whether related resources are removed, which would be useful for an openWorld deletion.

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 the baseline is 3. The description adds meaning beyond the schema by noting that IDs and numbers may be supplied in Persian/Arabic-Indic digits, which is directly relevant to the single 'id' parameter and not captured in the schema.

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?

States a specific verb and resource ('Delete a User') and names the concrete endpoint, so the operation is unambiguous. It does not explicitly distinguish itself from siblings like update_user or delete_account_user, but the verb+resource pairing is clear enough to route correctly.

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 versus update_user (e.g., deactivation) or delete_account_user, and no prerequisites beyond the auth note. The 'Platform app API key' hint weakly implies the platform-admin context versus the gapify_client_* family, but there are no explicit alternatives or exclusions.

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