crm_batch_update_leads

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

With no annotations provided, the description carries full burden but only states it's an update operation. It doesn't disclose behavioral traits like whether it's idempotent, requires specific permissions, has rate limits, returns partial results on failure, or what happens on invalid inputs. 'Update multiple leads' implies mutation but lacks critical operational details.

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 a single, efficient sentence with no wasted words. It's front-loaded and appropriately sized for a basic tool definition, though it could benefit from more detail given the complexity.

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 (batch update operation with nested schema), no annotations, no output schema, and 0% schema description coverage, the description is incomplete. It lacks information on behavior, error handling, return values, and usage context, making it inadequate for an AI agent to use effectively without guesswork.

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 description has 0 parameters (it doesn't explicitly list any), and schema description coverage is 0%, but the input schema is rich with nested properties. The description implies batch processing with 'inputs' but doesn't detail parameter meanings. However, with 0 parameters in the description, the baseline is 4 as it doesn't add semantic value beyond the schema's structure.

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 'Update multiple leads in a single request' clearly states the action (update) and resource (leads), but it's vague about scope and doesn't distinguish from siblings like 'crm_batch_update_contacts' or 'crm_update_lead'. It specifies 'multiple' and 'single request' which adds some specificity, but lacks detail on what 'update' entails compared to other batch operations.

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 is provided on when to use this tool versus alternatives. It doesn't mention prerequisites, when to choose batch update over individual updates (e.g., 'crm_update_lead'), or any constraints like rate limits or permissions. The description alone offers no usage context.

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