crm_create_contact_property

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action 'create' without detailing permissions required, side effects (e.g., impact on existing contacts), rate limits, or response format. For a mutation tool with 11 parameters and no annotations, this is a significant gap in transparency.

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 is front-loaded and appropriately sized for its minimal content, though this conciseness comes at the cost of detail. Every word earns its place, but the description is under-specified rather than concise.

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?

Given the tool's complexity (11 parameters, 5 required, no output schema, and no annotations), the description is completely inadequate. It lacks purpose differentiation, usage guidelines, behavioral context, and parameter explanations, making it insufficient for an agent to understand or invoke the 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?

Schema description coverage is 0%, meaning none of the 11 parameters are documented in the schema. The description adds no information about parameters, such as explaining what 'name', 'label', 'type', or other fields mean in the context of contact properties. This leaves all parameters semantically undefined, failing to compensate for the schema gap.

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 property' restates the tool name (crm_create_contact_property) with minimal elaboration, making it tautological. It specifies the verb 'create' and resource 'contact property' but lacks detail on what a contact property is or how it differs from similar tools like crm_create_company_property or crm_create_lead_property, failing to distinguish from siblings.

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. The description does not mention prerequisites, context, or exclusions, such as when to create a contact property versus using existing properties or other CRM tools like crm_create_contact. This leaves the agent without direction for appropriate tool selection.

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