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

No annotations are provided, so the description carries the burden. It discloses that the tool returns the updated user object and that a connected account must be used, but it does not address irreversibility, error cases, or required permissions beyond the connected account context.

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 four sentences, starting with the main action, then the prerequisite, return value, and cost. It is front-loaded and each sentence adds operational value.

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?

Given the simple delete operation, fully described parameters, and the presence of an output schema, the description covers the purpose, prerequisite, and return. It does not detail error conditions, but the tool's low complexity and structured schemas make this adequate.

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 already describes all three parameters clearly with 100% coverage. The description reinforces the behavior of clerk_instance_id by explaining the default behavior, but does not add additional syntax or format details beyond 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?

The description uses the verb 'Delete' with a specific resource ('passkey for a Clerk user') and identifies the required identifier ('by passkey id'). This clearly distinguishes it from sibling tools like clerk.delete_user_totp or clerk.delete_user_external_account.

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 explicitly instructs the agent to call clerk.get_connected_accounts first and explains how to target a specific connection via clerk_instance_id or default to the default account. It provides clear context for using the tool, though it does not mention exclusions or alternative tools for similar operations.

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