crm_create_contact

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Create' implies a write/mutation operation, but the description doesn't mention permission requirements, whether the operation is idempotent, what happens on duplicate emails, or what the response looks like. 'Validated properties' hints at input validation but doesn't specify validation rules or error behavior.

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 extremely concise at just 6 words, with no wasted language. It's front-loaded with the core purpose and includes the validation aspect as additional context. Every word serves a purpose.

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 creation tool with complex nested parameters (2 parameters with deep object/array structures), 0% schema description coverage, no annotations, and no output schema, the description is inadequate. It doesn't explain what happens after creation, what validation occurs, error conditions, or how to interpret results. The agent would struggle to use this tool effectively.

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 and 2 parameters (one required, one optional with complex nested structure), the description provides minimal parameter guidance. It mentions 'validated properties' which hints at the 'properties' parameter, but doesn't explain what properties are available, their formats, or the purpose of the 'associations' parameter. The description doesn't compensate for the complete lack of schema documentation.

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 the action ('Create') and resource ('contact'), and specifies 'with validated properties' which adds useful context about input validation. However, it doesn't explicitly differentiate from sibling tools like crm_batch_create_contacts or crm_create_lead, which would be needed for a perfect score.

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 provides no guidance on when to use this tool versus alternatives like batch creation tools or other CRM creation tools. It doesn't mention prerequisites, constraints, or typical use cases for creating individual contacts versus batch operations.

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