update_contact

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

With no annotations, the description carries the full burden but only states 'Update', implying mutation. It does not disclose whether fields are overwritten or merged, what permissions are needed, or what the output contains. The existence of an output schema is not addressed.

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 short sentence, making it concise, but it is under-specified and lacks essential details. It does not earn its place as it provides minimal value beyond the tool 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 presence of an output schema, return values are partially covered, but the description does not explain the update behavior or parameter usage. For an update tool with 5 parameters, the description is too incomplete for reliable agent use.

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?

The description adds no information about any of the 5 parameters. Schema description coverage is 0%, so the description should compensate but fails to explain contact_id, email, phone, first_name, or last_name. This leaves the agent without context for parameter usage.

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 the resource 'contact's details', distinguishing it from related tools like create_contact, delete_contact, and get_contact. However, it does not specify which details can be updated, relying on the schema for that information.

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 provides no guidance on when to use this tool versus alternatives such as create_contact or update_contact_relation. It does not mention prerequisites like the required contact_id parameter or any conditions for updating.

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