smokeball_create_lead

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only mentions authentication routing (JWT, tenant, company scope) but does not disclose whether the operation is destructive, idempotent, or what side effects occur. The actual creation behavior is undefined.

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 concise at four sentences, but it includes technical routing details that may not be necessary for an AI agent to understand usage. It could be more focused on the operational purpose rather than invocation mechanics.

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?

Although an output schema exists, the description does not mention what the tool returns after creation. For a creation tool, the return value (e.g., the created lead object) is critical context. Additionally, the single argument is insufficiently documented, making the tool incomplete for reliable 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 has a single 'arguments' parameter of type string with default '{}'. The description states it is a 'JSON string of arguments for the connector operation' but does not specify the expected structure, required fields, or examples. With 0% schema description coverage, this adds minimal guidance for constructing valid arguments.

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 names the operation 'create_lead' and mentions it's a Smokeball connector operation, which suggests its purpose. However, it does not explicitly explain what a lead is or how creation works, leaving the purpose somewhat vague. The name and platform tool reference provide minimal differentiation from sibling tools like smokeball_list_leads.

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 no guidance on when to use this tool versus alternatives (e.g., smokeball_create_contact, smokeball_create_matter). It lacks any context about prerequisites, when not to use it, or how it fits into workflows. The agent is left without any decision-making support.

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