crm_create_contact

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'validated properties' hinting at input validation, but doesn't describe what happens on success/failure, required permissions, rate limits, or whether the operation is idempotent. For a mutation tool with complex parameters, this is insufficient.

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 no wasted words. It's appropriately sized for a tool with a clear primary function, though the brevity contributes to gaps in other dimensions.

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 complex mutation tool with 2 parameters (one nested), 0% schema coverage, no annotations, and no output schema, the description is inadequate. It doesn't explain the return value, error handling, or the meaning of 'associations', leaving significant gaps for an agent to use the tool correctly.

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 must compensate. It only mentions 'validated properties' without explaining what properties are available, what 'associations' means, or the structure of nested objects. The description adds minimal value beyond the schema's field names.

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 'Create a new contact with validated properties' clearly states the action (create) and resource (contact), distinguishing it from sibling tools like crm_update_contact or crm_batch_create_contacts. However, it doesn't explicitly differentiate from other creation tools (e.g., crm_create_company) beyond the resource type.

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?

No guidance is provided on when to use this tool versus alternatives like crm_batch_create_contacts or crm_create_object. The description implies it's for creating single contacts, but lacks explicit context about prerequisites, dependencies, or scenarios where this tool is preferred.

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