cm_set_account_primary_contact

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

Annotations already declare 'idempotentHint: true', indicating safe repetition. The description adds the important constraint that the contact must be an 'existing administrator', which is behavioral context beyond the schema or annotations. No contradiction.

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?

Single sentence, no redundant words, front-loaded with the core function. Every word adds 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 operation (one parameter, no output schema, clear annotation), the description covers the essential prerequisite (existing administrator) and leaves no ambiguity. Complete for its 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 coverage is 100% with a single parameter 'email' described. The description adds the semantic constraint that the email must correspond to an existing administrator, which enhances understanding beyond the schema alone.

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 the action ('set'), the resource ('account's primary contact'), and the target ('existing administrator'). It effectively distinguishes from sibling tools like 'cm_get_account_primary_contact' (get vs set) and 'cm_set_client_primary_contact' (account vs client).

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 does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites or exclusions. While the context is simple, lack of when-to-use advice lowers the score.

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