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

With no annotations, the description carries the full burden for behavioral disclosure. It adds the return value (deleted domain id and deleted flag) and the prerequisite call, but does not mention whether deletion is permanent or any permission requirements, leaving some transparency gaps.

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 brief and front-loaded with the purpose, followed by a prerequisite, parameter guidance, return value, and cost in a logical order. Every sentence 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?

Given the tool's simplicity (2 parameters, output schema present), the description covers the essential operational steps, including the prerequisite call and return information. However, it omits any caveats (e.g., irreversible action or error handling), so it's not fully exhaustive.

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 schema covers both parameters, so the baseline is 3. The description adds meaning by explaining how to choose clerk_instance_id based on the connected account, which goes beyond the schema's default description.

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 specific verb 'Remove' and names the exact resource ('organization domain from a Clerk organization'), clearly distinguishing it from other domain-related tools like clerk.delete_domain. It directly states what the tool does in the first sentence.

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?

It explicitly instructs the user to call clerk.get_connected_accounts first and explains when to pass clerk_instance_id ('to target a specific connection') or omit it ('to use the default account'). This provides clear when-to-use guidance relative to connected account handling.

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