wc_create_account

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

With no annotations provided, the description carries the full behavioral burden. It clearly warns that the operation is mutating, explains that it refuses duplicate names, and states the dry-run-by-default behavior, which is critical for safe invocation.

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 one compact sentence that front-loads the mutating warning and packs in the key constraints: one per client, duplicate refusal, and dry-run default. Every clause adds meaningful guidance with no wasted words.

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 simple two-parameter creation tool, the description covers the essential safety and success criteria: mutating action, duplicate behavior, and confirmation flow. It does not describe what the tool returns on success or failure, but the absence of an output schema is partially offset by the schema's clear parameter documentation.

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 documents both parameters well. The description adds useful semantic context around account_name uniqueness and the one-per-client rule, but it does not substantially expand parameter meaning beyond what the schema provides.

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 precise action ('Create a WhatConverts account'), the resource type, and the agency convention of one account per client. It also distinguishes itself from siblings like wc_create_profile by explicitly scoping to accounts at the WhatConverts level.

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 gives clear contextual usage guidance by explaining the one-per-client agency convention and that the tool refuses duplicate names. However, it does not explicitly direct the agent to alternatives such as wc_create_profile when a profile is needed instead of a new account.

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