update_contact

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

No annotations provided, so description carries all burden. It discloses the write nature via [WRITE] and partial update behavior, but lacks details on permissions, side effects of archiving, or response format.

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?

Single sentence, front-loaded with [WRITE] indicator, no fluff. Every word earns its place.

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 9 parameters, nested objects, no output schema, and no annotations, the description is too terse. Missing: return value, error conditions, prerequisite that contact must exist, workflow context among siblings.

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 44%, so description must add value. The phrase 'only supplied fields change' clarifies that all optional parameters behave as partial updates, which goes beyond schema. However, individual parameter meanings are not elaborated.

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?

Description clearly states the tool updates an existing contact, with verb 'Update' and resource 'contact'. It distinguishes from sibling create_contact and get_contact by specifying it modifies an existing entity.

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?

Implied usage when modifying an existing contact's fields. Does not explicitly exclude other scenarios or list alternatives, but the purpose is clear enough for selection.

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