Create lead

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the description's 'Create' aligns with expected mutation. The description adds context about the lead being a prospect from an inbound enquiry but does not disclose additional behaviors such as required brand validation, potential side effects, or return values.

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, front-loaded sentence that efficiently conveys the tool's purpose and an example scenario. Every word contributes, and there is no redundant information.

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 is minimally adequate for a create tool, clarifying the target object (sales lead) and an example use case. However, with 7 parameters, no output schema, and minimal parameter guidance, it leaves gaps about required inputs and expected results, though annotations provide some 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 only 29% (only name and brand_id have descriptions), and the description adds no parameter information. It does not help clarify the seven parameters or indicate which are essential, failing to compensate for the low schema coverage.

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 tool creates a sales lead (prospect), using a specific verb and resource. It distinguishes from sibling lead tools like list_leads, update_lead, and convert_lead_to_client by focusing on creation, with an example of an inbound enquiry.

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 implies the tool is used when a new sales lead/prospect needs to be created, with an example source. However, it does not explicitly state when not to use it or mention alternatives like update_lead, leaving the usage guidance implicit.

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