create_person

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

No annotations are provided, so the description carries the full burden. It transparently discloses the automatic duplicate check, warning behavior, and force flag usage. It also notes a prerequisite for custom_fields (run sync_person_fields first). Missing details on authentication, rate limits, or success response, but core behavior is well covered.

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 minimal: two sentences that efficiently convey purpose and key behavior. It includes an important note (IMPORTANTE) to emphasize the duplicate detection. No extraneous content.

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?

With 7 parameters, no output schema, and no annotations, the description covers the duplicate detection nuance and force usage, but fails to specify the return value (e.g., created person object or ID) or error behavior. This is a notable gap for a creation tool.

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 100%, so baseline is 3. The description adds value by explaining the duplicate detection logic affecting email and phone parameters, and explicitly documents the force parameter's usage. It provides examples for owner_id and custom_fields, enhancing meaning beyond the schema.

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 'Cria um novo contato no Pipedrive', specifying the verb (create) and resource (contact/person). It also differentiates itself by highlighting the automatic duplicate detection, distinguishing from siblings like update_person.

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 usage guidelines by explaining the automatic duplicate search and the behavior when a duplicate is found. It also instructs on the force parameter: 'Use SOMENTE após confirmação explícita do usuário.' However, it does not explicitly contrast with alternative tools or state when not to use it.

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