reach_createANewContactV1

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

Discloses the double opt-in behavioral trait (pending status and confirmation email), but no annotations are provided to cover safety or permissions. Does not mention idempotency, data overwrite, or authentication needs.

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 sentences, no wasted words. The first sentence states the purpose, the second lists typical parameters, and the third adds an important conditional behavior. Efficient and focused.

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?

Covers the creation process and double opt-in effect, but lacks details on return value (no output schema), required permissions, and behavior if contact already exists. For a tool with 5 parameters and no annotations, more completeness would be beneficial.

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?

Adds context beyond the schema by describing parameters as 'basic information like name, email, and surname' and notes the impact of double opt-in on the creation process. Schema descriptions are minimal, so this adds value.

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?

Clearly states the action 'Create a new contact' and the system 'email marketing system'. It distinguishes from siblings by the explicit singular 'a new contact', but does not explicitly differentiate from the bulk create sibling 'reach_createNewContactsV1'.

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 on when to use this tool versus the bulk creation sibling or other contact tools. Does not mention prerequisites or scenarios where this endpoint is preferred.

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