create_lead

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

No annotations are provided, so the description carries the full behavioral burden, yet it says nothing. It omits whether fields are optional/required, what defaults apply, whether duplicates are rejected, what happens on missing data, or what the response contains.

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 single short sentence is front-loaded and waste-free, but this is under-specification rather than genuine conciseness. A one-line description for a 15-parameter creation tool earns no credit for 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 15-property, nested-object creation tool with no annotations and no output schema, the description is completely inadequate. It leaves the agent without the minimum context needed to call it correctly.

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 mentions no parameters at all while the schema has 15 properties with only 20% description coverage. With 0 required params and undocumented fields like lead_stage_id and lead_source_id, the description fails to compensate for 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?

"Create a new lead" states a verb and a resource, so the agent knows it's the lead-creation tool among the siblings. However, it essentially restates the tool name (create_lead) and offers no differentiation from create_contact/create_deal beyond the resource noun, so it sits at the minimum-viable level.

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?

There is no when-to-use guidance, no mention of prerequisites, and no reference to alternatives such as update_lead or create_contact. The agent is left to infer everything from the name alone.

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