Create Lead

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

With no annotations, the description must carry the burden. It reveals that the body is passed straight through and instructs to confirm field names, but it doesn't disclose authentication requirements, idempotency, error behavior, or response format. The 'Create' verb implies mutation but lacks deeper behavioral 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 two sentences with a link, front-loaded, and free of fluff. Every sentence 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 tool is simple but lacks return-value info and usage context. The docs link helps, but the description doesn't explain what the API returns or how to handle errors, and it doesn't address when to prefer this over sibling lead tools.

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 description already covers the body parameter well, including that it is raw JSON and to match docs. The tool description adds a docs link and repeats the 'matching fields' instruction. Since schema coverage is 100%, baseline is 3; the description doesn't add significant new meaning.

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 new lead' with a specific verb and resource. It doesn't explicitly distinguish from sibling tools like create_customer or convert_lead, but the purpose is unambiguous.

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 gives no guidance on when to use this tool versus alternatives like list_leads or convert_lead. It only states the action and points to docs, so the agent must infer usage from the name.

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