apollo_bulk_create_accounts

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

No annotations are provided, so the description must fully disclose behavior. It only hints at input format without discussing error handling, idempotency, rate limits, or partial failures common in bulk operations. This omission leaves agents unaware of critical behavioral traits.

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 sentence that is concise and front-loaded. It wastes no words but could benefit from additional structure to improve readability for a bulk operation with multiple parameters.

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?

Despite having an output schema (per context), the description lacks essential context for a bulk creation tool: no mention of limits, error responses, success confirmation, or handling of duplicate accounts. This incompleteness hinders safe and reliable execution.

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 coverage is low (33%), with only 'accounts' described in the schema. The description adds value by listing example fields ('name/domain/phone/etc.'), clarifying what dicts should contain. However, it does not explain 'run_dedupe' or 'append_label_names', leaving gaps.

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 purpose: 'Bulk-create CRM accounts.' This verb+resource format is specific and distinguishes it from siblings like 'apollo_create_account' (single account) and 'apollo_bulk_create_contacts' (different entity).

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, such as 'apollo_create_account' for single creation or 'apollo_bulk_create_contacts' for contacts. No context on prerequisites or conditions is given.

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