Add a lead

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

The description reveals behavioral traits beyond annotations: a default status 'new' with a pipeline flow, and optional fields ('value', 'lat/lng') that affect the pipeline and leads map. Annotations only indicate non-read-only and non-destructive, so this adds meaningful context.

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 concise sentences front-load the core purpose and key defaults, with no extraneous information. Every sentence provides value without redundancy.

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 complexity (10 parameters, no output schema), the description covers the essential creation logic and default behavior but omits details like return value, error handling, or duplicate prevention. It is adequate for a simple CRUD tool but incomplete for full contextual 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?

With only 10% schema description coverage, the description compensates partially by explaining 'name' (implied required), 'value', and 'lat/lng' usage. However, it fails to describe 7 out of 10 parameters (city, email, source, company, status, etc.), leaving significant gaps for an AI agent to understand proper invocation.

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 action ('Add a sales lead'), the target store ('project's leads store (crm/leads.json)'), and distinguishes from siblings like 'list_leads' or 'enrich_lead' by focusing on creation. The mention of default status and pipeline context adds specificity.

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 this tool is for initial lead creation by mentioning default status 'new' and pipeline stages, but it lacks explicit guidance on when to use it versus alternatives like 'enrich_lead' or 'convert_lead'. No exclusion criteria or alternative references are provided.

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