crm_batch_update_companies

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

No annotations are provided, so the description carries full burden. It only states the basic operation without disclosing any behavioral traits: no information about permissions required, rate limits, whether updates are atomic or partial, error handling for failed updates, or what the response contains. This is inadequate for a mutation tool with zero annotation coverage.

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 that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, with zero waste.

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 mutation tool with 1 parameter but deeply nested structure), lack of annotations, 0% schema description coverage, and no output schema, the description is severely incomplete. It fails to address critical aspects like behavioral traits, parameter meanings, or expected outcomes, making it inadequate for safe and effective use.

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%, meaning the schema provides no descriptions for parameters. The description adds no parameter semantics beyond the tool name—it doesn't explain the 'inputs' array structure, the 'id' field, or the 'properties' object with its numerous fields. This leaves all parameter meaning undocumented.

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 companies') and resource ('companies') with the specific context of batch processing ('in a single request'). It distinguishes from individual update tools like 'crm_update_company' by emphasizing batch capability, though it doesn't explicitly contrast with other batch tools like '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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, when batch updates are preferable to individual updates, or how it differs from other batch tools like 'crm_batch_update_contacts' or 'crm_batch_update_objects'.

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