crm_add_leads

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 discloses a batch limit, an ownership requirement, and privacy behavior ('Private to this user — no cross-user leak'). It does not detail error handling or idempotency, but the key behavioral traits are communicated.

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, front-loaded with the core action, and every phrase adds relevant detail. No fluff or 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 moderate complexity and lack of annotations or output schema, the description covers the essential invocation context: batch limit, owned group, privacy, and field guidance. It does not explain the return format, but this may be inferred as typical. Overall adequate for an agent to invoke the tool correctly.

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 coverage is 0%, so the description compensates by listing important fields (name, email, phone, company, address, city, map_url, website) and provides a concrete default instruction: 'has_website=false when no site.' This adds practical semantics beyond the raw schema, though not all parameters (e.g., tags, notes) are mentioned.

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 function: 'Add up to 25 leads to a group you own.' It specifies the action (add), the resource (leads), and the target (group), distinguishing it from sibling tools like crm_list_leads or crm_update_lead. The limit of 25 is also explicit.

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 when to use the tool (when adding leads to an owned group) and notes a prerequisite (ownership). It lacks explicit comparisons to alternatives, but the context is clear enough for basic selection.

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