crm_batch_create_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 states it's a create operation (implying mutation) but doesn't disclose behavioral traits like required authentication, rate limits, error handling for partial failures, or whether it's idempotent. The description is minimal and lacks critical context for a batch mutation tool.

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, clear sentence with zero wasted words. It's front-loaded with the core purpose and efficiently conveys the batch nature. Every word earns its place, making it highly concise.

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 tool's complexity (batch creation with nested parameters), lack of annotations, no output schema, and 0% schema description coverage, the description is inadequate. It doesn't explain input semantics, behavioral expectations, or output format, leaving significant gaps for an AI agent to use it 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?

Schema description coverage is 0%, so the schema provides no parameter descriptions. The description mentions 'multiple companies' but doesn't explain the 'inputs' parameter structure, nested fields (e.g., properties, associations), or required fields. It adds minimal value beyond the schema's structure, baseline 3 due to low coverage but insufficient compensation.

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 ('Create multiple companies') and resource ('companies'), and specifies it's a batch operation ('in a single request'). It distinguishes from single-create tools like 'crm_create_company' by emphasizing batch capability, though it doesn't explicitly contrast with other batch tools like 'crm_batch_create_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 (e.g., required permissions), limitations (e.g., batch size limits), or compare it to other batch tools (e.g., 'crm_batch_create_contacts' for contacts instead of companies). Usage is implied only by the tool name.

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