surveymonkey_create_contact

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

With no annotations, the description carries the full behavioral disclosure burden, but it only says 'creates a new contact' and lists parameters. It does not mention side effects, whether duplicate emails are rejected, permission requirements, or how this relates to contact lists, so an agent cannot predict non-obvious behavior.

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 short, front-loaded with the core action, and uses a compact Args list. Every sentence serves a purpose and there is no filler.

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 creation tool with an output schema, the basics are covered. However, it omits context about whether the contact is associated with a list and when to prefer this over sibling contact tools, so the agent has to infer important routing and side-effect details.

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 0%, but the description enumerates all three parameters and marks email as required while first/last are optional. This compensates for the lack of property descriptions, though it adds little beyond what the schema's required array and defaults already convey.

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 clear action and resource: 'Creates a new contact.' This distinguishes it from contact-list, survey, question, and other sibling operations. It does not explicitly compare itself to update_contact or create_contact_list, but the verb 'creates' plus 'contact' is unambiguous.

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?

No guidance is given for when to use this tool versus siblings such as create_contact_list, update_contact, or list_contacts. The description simply states what it does, leaving the agent to infer appropriate invocation context.

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