Set Contact Email

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

With no annotations, the description carries the full burden of behavioral disclosure. 'Save' communicates that this is a persistent write, and 'confirmed' adds an important precondition. However, it does not disclose whether an existing contact email is overwritten, what permissions are needed, or whether any side effects occur.

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, front-loaded sentence with no filler. Every word contributes meaning: the action, the confirmation precondition, and the target resource.

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 simple two-parameter tool with a fully documented schema and an output schema, the core invocation details are covered. Completeness is reduced by the lack of explicit side-effect disclosure and alternative tool routing, though these are not critical for basic 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?

Schema description coverage is 100%, so the schema already documents both parameters. The description adds minimal semantic value beyond the schema, mainly reinforcing the 'confirmed' constraint already present in the email parameter description.

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 uses a specific verb ('Save') with a precise object ('confirmed email address') and target ('on a contact'). This clearly distinguishes it from sibling tools like suggest_email and send_email, which suggest or send rather than persist an address.

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 word 'confirmed' implies the tool should be used only after the user has verified the email address, and 'on a contact' implies an existing contact. However, no alternatives are named and no explicit when-not-to-use guidance is provided, so usage context is only implicit.

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