reach_createANewContactV1

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

Discloses double opt-in behavior (pending status, confirmation email) but lacks details on idempotency, duplicate handling, or return format. No annotations exist, so description provides moderate value.

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 concise sentences with no fluff. Front-loaded with core purpose, then context, then edge case (double opt-in). Efficient use of text.

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 creation and double opt-in but omits output format, error conditions, and additional constraints. Adequate for a simple create tool but not fully complete given no output schema.

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 minimal descriptions (e.g., 'email parameter'). The description adds no extra meaning beyond listing fields; baseline of 3 is appropriate as schema already documents parameters.

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 'Create a new contact in the email marketing system' with specific fields (name, email, surname). Distinct from sibling reach_createNewContactsV1 (bulk) and reach_createANewContactSegmentV1 (segment).

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?

Implies usage for single contact creation but does not explicitly guide when to use this vs bulk create (reach_createNewContactsV1). No exclusion criteria or prerequisites mentioned.

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