reach_createNewContactsV1

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

The description adds behavioral context about double opt-in leading to a pending status and confirmation email. However, with no annotations provided, it could disclose more, such as whether existing contacts can be overwritten or the specific required permission scope.

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 concise at three sentences, with the first sentence stating the core purpose, the second listing example fields, and the third covering a behavioral detail. No unnecessary information is included.

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 6 parameters, only three are mentioned in the description. The required 'profileUuid' is omitted. Also, no output schema exists, and the description does not explain what the tool returns (e.g., contact ID). Missing error conditions or duplicate handling.

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%, so the baseline is 3. The description mentions name, email, and surname but does not add meaning beyond the schema. It omits reference to the required 'profileUuid' parameter and optional fields like phone and note, which are documented in 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 clearly states the tool creates a new contact in the email marketing system, specifying it handles basic info like name, email, and surname. However, it does not differentiate from the sibling 'reach_createANewContactV1', which likely has the same purpose.

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 gives a general usage indication but lacks any guidance on when to use this tool versus alternatives or when not to use it. No exclusions or prerequisites are mentioned beyond the required fields in the schema.

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