contacts_create

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

There are no annotations, so the description must fully disclose behavioral traits. It states only that the tool creates a contact, but does not mention permissions, default address book behavior, duplicate handling, or whether changes are reversible. With no annotation support, this leaves the agent with significant uncertainty about the operation's side effects.

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, front-loaded sentence with no filler words. Every word contributes to the core message, making it efficiently concise for such a simple tool.

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 that there are 6 parameters, no schema descriptions, and no annotations, the one-sentence description is insufficient for fully correct invocation. The output schema covers return values, but the description fails to clarify ambiguous field meanings, optional-field handling, or the relationship to batch creation, leaving the overall context incomplete.

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%, so the description must add meaning to the parameters. It lists 'name, email, phone, organization, and title,' but does not map 'name' to the actual given_name and family_name fields, and it omits family_name entirely. This is ambiguous and provides minimal value beyond the raw property names 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 uses the verb 'Create' with the resource 'contact' and lists key fields (name, email, phone, organization, title), making the primary purpose clear. It is distinguishable from sibling tools like contacts_update and contacts_delete by the explicit 'new contact' framing, though it does not explicitly distinguish itself from contacts_batch_create.

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 implies usage: use this tool when you want to create a single new contact. However, it gives no explicit guidance on when to prefer this over contacts_batch_create for multiple contacts, nor any prerequisites, limitations, or alternative tools for similar tasks.

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