create_contact

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

No annotations are provided, so the description carries the full burden. It signals a mutation only through the word 'Create' and gives no information about side effects, duplicate/tax-ID conflicts, error behavior, required permissions, or what the call returns --- all of which matter for a 9-parameter create tool with nested objects.

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?

Six words and a version tag for a tool with 9 parameters, a nested address object, and an array of contact persons. Nothing is wasted, but the definition is grossly under-sized relative to the operation's complexity rather than truly concise.

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 no annotations, no output schema, and a nested-object payload, the description should explain creation semantics (what is returned, duplicate handling, whether type defaults apply). The API-version parenthetical is the only extra context provided, leaving significant gaps.

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% and includes notable guidance (the 'code' vs legacy 'vatnumber' caveat, the type enum, nested contactPersons). The description adds nothing on top of the schema, so the baseline 3 applies.

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 states a specific verb and resource ('Create a new contact'), which an agent can match to the create/list/update/delete_contact family. It does not explicitly distinguish itself from siblings such as update_contact or create_contact_group, so it stops short of a 5.

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?

There is no guidance on when to use this rather than update_contact (for an existing contact) or create_contact_group, nor any prerequisites, duplicate-handling notes, or mention that only 'name' is required. The agent must infer everything from the name alone.

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