create_lead

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

Since there are no annotations, the description carries the burden of behavioral disclosure. It importantly discloses the preview behavior ('Preview unless confirm=True') and explains the role of extra_values for setting fields not modeled by the helper. It does not however describe side effects, permissions, or error handling, so a 4 is appropriate.

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 two sentences, front-loaded with the primary purpose. The second sentence provides key behavioral details without unnecessary verbosity. Every word earns its place.

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?

The description covers the essential purpose, preview mode, and extra_values handling, and an output schema exists for return values. It could benefit from a brief note on whether the tool requires authentication or how preview results are returned, but overall it is reasonably complete for a create tool with 7 parameters.

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. It adds meaning for two non-obvious parameters: confirm (preview vs actual create) and extra_values (custom fields and mandatory fields). Other parameters like name, email, and phone are self-explanatory from their names and types.

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 'Create a CRM lead/opportunity (crm.lead)', using a specific verb and resource. It distinguishes itself from sibling tools like create_contact or create_task by specifying the crm.lead model.

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 clear context that this tool is for creating CRM leads/opportunities, but does not explicitly mention when not to use it or alternatives like create_contact. The guidance on using extra_values hints at how to handle custom fields, but lacks explicit exclusion criteria.

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