Set Contact Name

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

Annotations already declare readOnly=false, idempotent=true, destructive=false, and openWorld=true, so the safety profile is covered structurally. The description adds nothing beyond the purpose line: no note that an existing name is overwritten, no auth/account scoping (the account param defaults to the single configured brand_a), and no rate-limit or failure context.

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?

A single, front-loaded sentence with no filler, which is appropriate for a narrow setter. It is efficient, though the terseness contributes to the transparency and parameter gaps noted elsewhere.

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 three-parameter setter with annotations covering the safety profile and no output schema, the definition is minimally workable. It omits what the tool returns or confirms, how it behaves on an invalid contact_id, and any account/scope caveats the agent would need.

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 67%: name and account are documented in the schema, but contact_id has no description anywhere. The description does not compensate by clarifying what contact_id refers to (WhatsApp contact identifier) or the account default, leaving one parameter semantically thin.

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?

States a specific verb (Update) and resource (display name of a WhatsApp contact in SendPulse), which separates it from cousins like sendpulse_set_contact_variable and sendpulse_set_contact_tags. It stops short of explicitly naming a sibling, so it is clear but not maximally differentiated.

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?

There is no guidance on when to use this versus set_contact_variable, set_contact_tags, or create_contact, and no prerequisites are stated. The agent must infer usage entirely from the name and description.

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