crm_batch_update_leads

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

No annotations are provided, so the description carries full burden. It states it's an update operation but lacks critical behavioral details: whether it requires specific permissions, if updates are partial or full, error handling for invalid inputs, rate limits, or what the response contains. 'Update' implies mutation, but without safety or outcome 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?

Extremely concise with a single, clear sentence that front-loads the core purpose. No wasted words or redundant information, making it easy to parse quickly.

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?

Incomplete for a mutation tool with no annotations and no output schema. The description lacks details on behavioral traits, error handling, response format, and usage context. Given the complexity (batch update with nested properties) and absence of structured data, it should provide more guidance to be fully helpful.

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 description coverage is 0%, but the description adds minimal value beyond the schema. It hints at 'multiple leads' and 'single request,' aligning with the 'inputs' array parameter, but doesn't explain parameter structure (e.g., that 'inputs' contains objects with 'id' and 'properties') or provide examples. Baseline is 3 due to low coverage, but description compensation is weak.

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 ('Update multiple leads') and resource ('leads'), specifying it's a batch operation ('in a single request'). It distinguishes from single-update tools like 'crm_update_lead' but doesn't explicitly differentiate from other batch tools like 'crm_batch_update_companies' or 'crm_batch_update_contacts'.

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 guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing lead IDs), compare to single-update tools, or specify use cases like bulk edits. The agent must infer usage from the name and context alone.

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