crm_create_lead

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. While 'Create' implies a write/mutation operation, the description doesn't address critical aspects like required permissions, whether the operation is idempotent, what validation entails, error conditions, or what happens on success. The mention of 'validated properties' hints at input validation but lacks specifics.

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, front-loading the core purpose without any wasted words. Every word earns its place, making it easy to parse quickly despite its brevity.

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 2 parameters (including complex nested objects), 0% schema description coverage, no annotations, and no output schema, the description is severely inadequate. It doesn't explain what 'validated properties' means, doesn't describe the response format, and provides no behavioral context for a mutation operation.

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), the description provides minimal parameter information. It mentions 'validated properties' which relates to the 'properties' parameter but doesn't explain what validation means or describe the 'associations' parameter at all. The description fails to compensate for the complete lack of schema descriptions.

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 ('a new lead'), making the purpose immediately understandable. However, it doesn't differentiate this from sibling tools like 'crm_batch_create_leads' or 'crm_create_contact', which would require mentioning this is for single lead creation with property validation.

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. There's no mention of prerequisites, constraints, or comparison with sibling tools, leaving the agent with insufficient context for proper tool selection.

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