create_contact

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

No annotations are provided, leaving the description fully responsible for behavioral disclosure. It only mentions optional tags and custom fields, but does not explain the return value, duplicate handling (e.g., what if email exists), permissions required, or whether the operation is reversible. This is a significant gap for a mutating tool.

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 a single, concise sentence of 13 words, front-loading the core purpose. It contains no filler or redundant information and is well-structured.

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 7 parameters, one nested object, no output schema, and no annotations, the description is incomplete. It does not mention what happens on success (e.g., returned contact ID), error conditions, or any prerequisite context. The schema covers parameters, but the broader operational context is missing for a tool of this complexity.

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 100%, so the baseline is 3. The description adds no extra meaning beyond what the schema already provides; it merely restates that tags and custom fields are optional, which is already visible from the required fields list.

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 action ('Create a new contact') and the resource ('CRM'), making the purpose immediately evident. It also distinguishes itself from sibling tools like update_contact and get_contacts by specifying 'new'.

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?

Usage is implied: use this when you want to create a new contact. However, there is no explicit guidance on when to use alternatives like update_contact for existing contacts or add_tags for adding tags later, so it falls to 'implied usage' rather than clear context.

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