create_contact

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals a meaningful behavioral trait: the write is read back and rolled back if altered by the server, so success means the stored card matches what was sent. This goes well beyond a generic 'create' description, though it doesn't cover auth, failure modes, or return 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?

Two short sentences with a clear front-loaded purpose and a valuable behavioral guarantee. Every sentence adds information; no redundancy or bloat.

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?

The description is adequate for a simple create operation and gives a meaningful integrity guarantee, but it omits usage routing, parameter semantics, return shape, and error/rollback details beyond the core guarantee. Since there is no output schema or annotations, these gaps leave the agent partially to inference.

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 should compensate for the six parameters. It adds only entity-level context ('connect contact') and doesn't explain any field, especially ambiguous ones like 'addressbook' or 'organisation.' The parameter names are somewhat self-explanatory but that is schema value, not description value.

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: 'Add a contact.' This clearly distinguishes the tool from siblings like create_event, create_task, and search_contacts without requiring the agent to inspect schemas.

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 gives no guidance on when to use this tool versus alternatives such as search_contacts or list_collections. There is no mention of prerequisites, when not to use it, or how it relates to other contact-related tools. Usage is only implied by the action word 'Add.'

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