apollo_create_contact

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

With no annotations, the description carries full burden. It discloses dedup behavior via run_dedupe and the escape hatch via extra parameter. Lacks info on permissions or rate limits but is adequate for a create 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?

Two concise sentences front-load the purpose and add key behavioral details without redundancy. 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 the standard contact fields and the existence of an output schema, the description is sufficiently complete. The extra parameter covers custom fields. Could mention optionality, but overall adequate.

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 only 8% (only extra has a description). The description adds meaning by explaining extra as an escape hatch and that common fields are explicit. However, for 12 parameters, more guidance on required/optional fields would help.

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 contact' with specific verb and resource, and distinguishes from bulk sibling by mentioning 'single'. It also adds dedup behavior.

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 implies usage for creating a single contact but does not explicitly contrast with alternative tools like apollo_bulk_create_contacts or apollo_update_contact. No when-not-to-use guidance.

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