crm_update_contact

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

With no annotations provided, the description carries full burden but offers minimal behavioral context. 'Update' implies mutation, but it doesn't disclose permission requirements, whether updates are partial or complete, validation failure behavior, or what the response contains. The mention of 'validated properties' hints at validation but doesn't explain it.

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, efficient sentence with zero wasted words. It's appropriately sized and front-loaded with the core action.

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?

For a mutation tool with no annotations, 0% schema description coverage, no output schema, and complex nested parameters, the description is inadequate. It should explain validation, update behavior, response format, and error handling to be complete.

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 0%, so the description must compensate but only adds minimal context. It mentions 'validated properties' which relates to the 'properties' parameter, but doesn't explain the structure or validation rules. The schema documents 2 parameters with rich nested properties, but the description doesn't clarify their semantics 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 the verb 'update' and resource 'existing contact', making the purpose unambiguous. It distinguishes from sibling tools like crm_create_contact by specifying 'existing', but doesn't explicitly differentiate from other update tools like crm_update_company or crm_update_lead.

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?

No guidance is provided about when to use this tool versus alternatives like crm_batch_update_contacts or crm_update_object. The description mentions 'validated properties' but doesn't explain what validation entails or any prerequisites for successful updates.

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