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 of behavioral disclosure. It only conveys the mutating action and the vCard format; it does not disclose whether creating is idempotent, what happens if the address book does not exist, or what the tool returns. This is a significant gap for a write operation.

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 efficient sentence with the action and format front-loaded. Every word adds value, and there is no redundant or extraneous 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?

For a straightforward create operation with fully documented parameters, the description is minimally adequate. However, with no output schema and no annotations, it does not mention the required addressbook_url context or any return/error behavior, so an agent must rely on the schema for operational completeness.

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 schema already documents all eight parameters. The description adds no new semantic detail beyond listing a few field names, and 'other details' is vague. The baseline of 3 is appropriate because the schema, not the description, carries the parameter meaning.

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 precise action ('Create a new contact') and a specific resource ('vCard'), and enumerates representative fields like name, email, phone, and organization. This clearly distinguishes it from sibling tools such as update_contact, delete_contact, and create_event.

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 explicit statement of when to use this tool versus update_contact or delete_contact, but the verb 'Create' and the contact resource make the intended use reasonably inferable. It does not mention prerequisites such as needing an existing address book, which would be useful.

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