create_lead

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

The description provides no behavioral context beyond the basic create action. Since annotations are absent, it should disclose aspects like required fields (only 'name' per schema), the fact that other fields are optional, and what the response contains; none are mentioned. There is also no mention of authorization, side effects, or error conditions, so the agent is left with minimal insight into the tool's runtime behavior.

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, abridged sentence with no redundant words, achieving high conciseness. It is front-loaded with the action and resource, so it is easy to scan. The extreme brevity sacrifices detail, but conciseness itself is excellent.

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 create tool with 11 parameters and no output schema, this description is severely under-specified. It does not mention the required 'name' field, what happens on success (e.g., return value), or how the various optional contact/pipeline fields are used. The agent would need to rely solely on the schema and siblings, making the description incomplete for safe invocation.

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 input schema already provides descriptions for all 11 parameters, so the description adds no additional meaning. It does not explain relationships between parameters (e.g., pipeline_id vs pipeline_stage_id) or any defaults. However, with 100% schema coverage, the baseline score of 3 is appropriate.

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 uses the specific verb 'Create' and identifies the resource as 'a new CRM deal (lead)', clearly distinguishing this from sibling update/delete/list tools for leads and other entities. It also explicitly equates deal and lead, which removes ambiguity.

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 guidance is provided regarding when to use this tool versus alternatives such as update_lead or create_task. The description only states the action, leaving the agent to infer usage from the name and sibling context. This fails to convey conditions, prerequisites, or exclusions.

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