crm_create_lead

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 fails to describe critical traits like required permissions, mutation effects (e.g., data persistence), error handling, or rate limits. This leaves significant gaps for a creation tool.

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 that is front-loaded with the core action. There is no wasted verbiage, making it appropriately concise. However, it could benefit from more structured detail given the tool's complexity.

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 (2 parameters with nested objects, no output schema, and no annotations), the description is inadequate. It lacks details on parameter usage, behavioral expectations, and output, leaving the agent with insufficient information to invoke the tool correctly in context.

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 for undocumented parameters. It only vaguely references 'validated properties', without explaining the two parameters ('properties' and 'associations') or their structures. This adds minimal meaning beyond the schema, failing to address the coverage 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 states the action ('Create') and resource ('new lead'), which clarifies the basic purpose. However, it doesn't specify what distinguishes this from sibling tools like 'crm_batch_create_leads' or 'crm_create_contact', making it vague in differentiation. The mention of 'validated properties' adds some specificity but remains ambiguous.

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 explicit guidance is provided on when to use this tool versus alternatives such as batch creation or other CRM create operations. The description implies usage for creating leads with validation, but it lacks context on prerequisites, exclusions, or comparisons to sibling tools, offering minimal direction.

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