apollo_create_account

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

With no annotations, the description must disclose behavioral traits. It states 'Create' implying a write operation, but does not mention idempotency, side effects, or outcomes (e.g., whether a duplicate is created if run_dedupe is false). Key parameters like run_dedupe and owner_id are left unexplained, leaving the agent unaware of potential impacts.

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 extremely concise, containing only two sentences. The first sentence states the purpose, and the second provides a key usage tip about 'extra'. No wasted words.

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 8 optional parameters and no annotations, the description is incomplete. It does not explain the output (despite an output schema existing), does not discuss error conditions, and lacks context about when to create versus update. The agent would need to infer critical details from the parameter names alone.

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 explains the 'extra' parameter's purpose (for additional fields), but does not describe the meaning of the other 7 explicit parameters (name, phone, domain, owner_id, run_dedupe, raw_address, account_stage_id). Schema coverage is 0%, so the description fails to compensate adequately.

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 'Create a single CRM account', which is a specific verb and resource. It distinguishes from bulk creation by emphasizing 'single', and hints at handling extra fields via 'extra' parameter. This sets it apart from sibling tools like apollo_bulk_create_accounts.

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 implicit guidance by mentioning 'single' versus bulk creation, but does not explicitly state when to use this tool over alternatives like apollo_update_account or apollo_bulk_create_accounts. It also lacks prerequisites or contextual cues about required fields or permissions.

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