crm_create_lead_property

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 but fails completely. It doesn't indicate whether this is a safe operation, what permissions are required, whether it's idempotent, what happens on failure, or what the response looks like. For a mutation tool that creates new data structures, this lack of behavioral context is a critical 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?

The description is maximally concise - a single sentence with no wasted words. While this conciseness comes at the expense of completeness, the structure is clear and front-loaded with the core action. Every word in 'Create a new lead property' serves a purpose, making it efficient if inadequate.

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 complexity (11 parameters, mutation operation, no annotations, no output schema), the description is completely inadequate. It doesn't explain what a lead property is, how it's used, what the parameters mean, what happens after creation, or provide any context for this significant data definition operation in a CRM system.

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?

The description provides no information about any of the 11 parameters, despite 0% schema description coverage. It doesn't explain what 'name', 'label', 'type', 'fieldType', 'groupName' or any other parameters mean in the context of creating a lead property. With 11 parameters (5 required) and no schema descriptions, the description fails to add any semantic value.

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 lead property' is essentially a tautology that restates the tool name 'crm_create_lead_property' with minimal elaboration. It specifies the verb 'create' and resource 'lead property', but doesn't distinguish this from sibling tools like 'crm_create_company_property' or 'crm_create_contact_property', nor does it explain what a 'lead property' actually is in this CRM context.

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 zero guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, when this operation is appropriate, or what alternatives exist among the many sibling CRM tools. For example, it doesn't clarify when to create a lead property versus using existing properties or other lead-related tools.

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