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

With no annotations provided, the description carries the full burden. It discloses the prerequisite (get_connected_accounts), the behavior of the optional clerk_instance_id (target specific connection or default), and the return value (updated user object). It could additionally disclose permanence or permission requirements, but the provided details are useful.

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 three sentences, front-loaded with the core action, and includes only essential information: prerequisite, optional parameter behavior, return value, and cost. No unnecessary words or repetition.

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?

The tool is simple, and the description covers the key behavioral aspects: the action, prerequisite, optional parameter handling, and return value. An output schema exists, so the return structure is available. This is complete for the tool's complexity.

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%, so the schema already fully documents all parameters. The description adds no new parameter meaning beyond what is in the schema, simply restating the clerk_instance_id behavior, which aligns with the baseline score.

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 that the tool deletes a Web3 wallet for a Clerk user, using a specific verb and resource. It distinguishes from sibling tools (e.g., delete_user_passkey, delete_user_totp) by explicitly naming the resource type.

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 instructs the agent to call clerk.get_connected_accounts first, providing clear context for the optional clerk_instance_id parameter. However, it does not explicitly mention alternative tools or exclusion criteria, though the purpose is self-evident.

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