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 burden. It states the tool creates a lead, which is a clear behavioral indication. However, it does not disclose potential side effects, idempotency, or error scenarios. It is minimally adequate but not rich in detail.

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 extremely concise at two sentences, with the primary purpose stated first. Every sentence adds value without redundancy. It is well-structured and front-loaded.

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 14 parameters, zero schema descriptions, and no annotations, the description leaves many aspects uncovered. An output schema exists, so return values are not required, but the description fails to guide on tool selection or explain most parameters. The tool is missing essential context for a full understanding.

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 schema has 14 parameters with zero description coverage (0%). The description only adds meaning for name fields and contact fields, covering only about 14% of parameters. Other fields like case_type, lead_provider, status, etc. are left unexplained. The description does not compensate nearly enough 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's purpose: 'Create a new lead/intake.' This is a specific verb-resource pair. However, it does not distinguish between sibling tools like create_lead_full and create_lead_obo, so it scores a 4 rather than a 5.

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 some parameter guidelines ('FirstName+LastName or FullName required', 'CellPhone and Email strongly recommended') but gives no indication of when to use this tool versus alternatives or when not to use it. No explicit usage context or exclusions are provided.

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