autotask_update_contact

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

No annotations provided, so the description carries the burden. It discloses partial update behavior ('Pass only the fields you want to change') and field naming convention ('match the Autotask REST API exactly'). However, it does not mention error handling, permissions, or side effects. This is adequate but not exceptional.

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 sentences with zero wasted words. The first sentence states purpose, the second adds critical usage guidance (partial update) and naming convention. Efficient and well-structured.

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 15 parameters, no output schema, and no annotations, the description explains the update pattern and field naming. It does not mention return value (e.g., updated contact object or success status), which may be needed for an agent to handle responses. Adequate but not completely thorough.

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% with clear descriptions for each parameter. The description adds 'Field names match the Autotask REST API exactly', which is marginally useful. No additional semantics beyond schema, so baseline 3 is appropriate.

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 'Update an existing contact in Autotask', using a specific verb ('Update') and resource ('contact'). This distinguishes it from sibling tools like autotask_create_contact (create) and autotask_search_contacts (search).

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 explicitly says 'Pass only the fields you want to change; all non-id fields are optional', which tells the agent when to use this tool (update existing) and how to use it (partial updates). It implicitly differentiates from autotask_create_contact. Lacks explicit when-not-to-use or alternatives.

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