wc_create_profile

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 explicitly flags the operation as MUTATING, explains the duplicate-name refusal and its protective purpose, and discloses the dry-run default. This is strong and actionable transparency.

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?

Three concise sentences, each earning its place: mutation warning, core purpose, duplicate guard, and dry-run behavior. The warning is front-loaded, and there is no filler or redundant restating of the tool name.

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 description covers purpose, mutation risk, safety defaults, and a key failure mode. The only meaningful gap is that it does not describe what the tool returns or how the agent should confirm success, and there is no output schema to fill that gap.

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 covers confirmed and account_id well, and the description adds meaning for profile_name by explaining the duplicate-name constraint. It stops short of describing naming rules or the response, but it adds value 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 states a specific action ('Create a profile'), a specific resource ('inside an existing WhatConverts account'), and distinguishes itself from sibling tools like wc_create_account and the GA4/GTM creators. An agent can clearly tell what this tool does and what it does not do.

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 clearly situates use within an existing WhatConverts account, implying the account should first be obtained via wc_list_accounts. It does not explicitly name sibling alternatives or state when not to use it, but the 'existing account' qualifier provides practical routing guidance.

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