update_person

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

With no annotations, the description should fully disclose behavior. It mentions the pre-update check and additive behavior, but fails to disclose the destructive potential of the 'force' parameter, the prerequisite for 'custom_fields' (sync_person_fields), and the nature of updates for other fields (overwrite vs. merge).

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 two concise sentences plus an important note. Every sentence adds meaningful information, with the core action upfront and critical behavioral notes following without redundancy.

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 7 parameters, no output schema, and no annotations, the description is incomplete. It omits the 'force' parameter's implications, the prerequisite for 'custom_fields', the return value or side effects, and does not differentiate the update behavior for organization field. Sibling tools like 'create_person' further highlight missing context.

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 100% (baseline 3). The description adds value by clarifying that email and phone are added, not replaced. However, it does not describe 'force' or 'custom_fields' beyond what the schema says, missing an opportunity to add further semantic context.

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 updates a contact with specific fields (name, email, phone, organization). It distinguishes from sibling tools like 'create_person' and other update tools by specifying the resource and the additive behavior for email and phone.

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 warns about checking existing fields and overwrites, and clarifies email/phone are added. However, it omits guidance on when not to use the tool (e.g., for replacing email/phone) and doesn't mention the 'force' parameter's crucial role in bypassing warnings.

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