create_contact

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

With no annotations, the description carries the full burden. It discloses the tag limit ('max 5 on creation') and field applicability (e.g., company_name required for company records), but it does not mention permissions, idempotency, or what happens on validation failure. The provided details are useful but not comprehensive.

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 compact and front-loaded with the purpose, followed by an ordered Args list where each line is a meaningful parameter explanation. There is no wasted text, and the structure is easy to parse.

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 covers the parameters and conditional requirements well, and an output schema exists so return details are not needed. It lacks explicit guidance on when to use this versus sibling tools, but for a 9-parameter creation tool with a required record_type, the provided information is largely sufficient for invocation.

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%, but the description fully compensates by explaining every parameter: record_type values, conditional name fields, email/phone modifier enumerations, and tag limits. This adds significant meaning beyond the bare schema titles.

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 'Create a new contact (person or company)' with a clear verb and resource, and the parenthetical distinguishes contact creation from other creates like create_note or create_deal. This is specific and unambiguous.

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 when a new contact needs to be created, and the 'person or company' distinction provides some context. However, it does not explicitly mention when to use this tool versus update_contact or delete_contact, nor does it offer exclusions or alternative tool references.

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