Add a lead

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

Annotations already indicate the tool is not read-only and not destructive. The description adds context about the pipeline stages and the location of data, but does not disclose additional behavioral traits such as idempotency, authentication needs, or side effects beyond creation.

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?

Two sentences, no wasted words, appropriately front-loaded with the core action. Every sentence adds meaningful 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?

Given the tool has 10 parameters and no output schema, the description covers the essential aspects: what it does, where it stores data, default status, and optional fields for advanced features. It is mostly complete for a creation tool, though it could explain more about other parameters.

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 coverage is only 10% (only 'value' has a description). The description explains the purpose of 'value' and 'lat/lng' for pipeline value and leads map, but other parameters like 'name', 'email', 'city', 'company', 'source' are left unexplained, partially compensating but not fully.

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 adds a sales lead to a specific store (crm/leads.json), specifies the default status and pipeline stages, and mentions optional fields that power other features. It unambiguously distinguishes from siblings like convert_lead or set_lead_status.

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 explicit guidance on when to use this tool versus alternatives (e.g., convert_lead, enrich_lead). The description focuses on what the tool does but does not specify context, when not to use it, or prerequisites.

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