Contract Testing: Admin Delete User

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=true, so the description adds little beyond what is already structured. It does not disclose irreversibility, cascading effects on related data, or any security/permission requirements beyond the already present '(admin)' label.

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 short and front-loaded with the core action, followed by a minimal parameter list. It contains no filler, though the parameter list duplicates the schema; still, it remains appropriately sized for a simple one-parameter tool.

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 single-parameter admin delete with no output schema, the description covers the essential action and parameter. However, it omits any mention of error cases, what happens to the deleted user's data, or how this interacts with team memberships and roles, leaving some ambiguity in a destructive Admin operation.

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 a single parameter userId, and the schema itself provides the description 'UUID of the user'. The description only repeats this information without adding meaning such as format, examples, or how to obtain the UUID.

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 states a specific verb and resource: 'Delete a user account (admin).' This clearly distinguishes it from sibling tools like admin_update_user, admin_create_user, and admin_invite_users, so an agent can identify the correct operation without opening the schema.

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 provides no explicit guidance about when to use this tool versus alternatives, nor does it mention prerequisites or conditions. The 'admin' qualifier hints at scope but does not say, for example, when deletion is preferred over updating or deactivating a user.

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