create_contact

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

No annotations provided, so the description bears full responsibility. It does not disclose return value, error handling, or side effects (e.g., whether creation triggers workflows). It only lists parameters. For a creation tool, this is a significant gap.

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?

Very concise: one lead sentence stating purpose and requirement, followed by a clean 'Args:' section. Every sentence adds value. No redundancy.

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 tool has 7 parameters and no annotations or output schema. The description explains parameters adequately but omits behavioral context (return value, errors). For a create operation, knowing the response is important. It is minimally complete but has 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?

With 0% schema description coverage, the description adds crucial meaning: it explains 'basics' for names/email/phone, 'labels like [Lead, Enterprise]' for tags, 'internal notes' for notes, and 'custom fields' with example for additional_data. It also clarifies the required condition. This is helpful but lacks format constraints.

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 clearly states 'Create a CRM contact' with a specific verb and resource. It distinguishes from siblings like update_contact, delete_contact, and bulk_create_contacts by focusing on single contact creation.

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 notes that 'either email or phone_number is required', giving a key condition. However, it does not provide explicit guidance on when to use this tool versus alternatives (e.g., bulk_create_contacts for multiple contacts, update_contact for existing), nor does it mention prerequisites or constraints like duplicate handling.

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