contacts_update

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

With no annotations provided, the description carries full responsibility for disclosing behavioral traits, but it only states 'Update a contact'. It does not mention whether updates are partial (only provided fields change), whether missing fields are preserved, or any permissions needed. This lack of detail is a significant gap for a mutation tool.

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 extremely concise, consisting of two short sentences with no redundant information. It front-loads the core action and immediately provides a practical hint for obtaining the resource name.

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 the tool has 7 parameters and an output schema, the description is too brief. It does not explain update semantics, the effect of omitting fields, or any prerequisites beyond the resource name. The output schema exists but does not substitute for missing behavioral 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 description coverage is 0%, and the description only elaborates on resource_name, missing explanations for the other six parameters (email, phone, title, etc.). The description does not clarify that only specified fields are updated, so it fails to compensate for the schema's lack of detail.

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 a contact' with a specific verb and resource, distinguishing it from siblings like contacts_create and contacts_delete. It also provides a clear source for the required resource_name parameter.

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 implies usage context by specifying 'Resource name from contacts_search/contacts_list', indicating the user should first search/list to obtain the identifier. However, it does not explicitly state when to use this tool over alternatives or provide exclusions, leaving usage guidance implied rather than explicit.

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