Toggle auto-add for new contacts

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

Annotations already indicate idempotence and non-destructiveness. The description adds context about the companion default ('autoAdd: true') and explains the effect of each mode. No contradictions.

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 concise sentences with no redundant information. Every word earns its place, and the structure is front-loaded with the core action.

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 simple toggle nature, low parameter count, and presence of an output schema, the description is complete. It could briefly mention the return value, but that is covered by the output schema.

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 input schema already describes the boolean parameter with 100% coverage. The description adds value by specifying the companion default and suggesting manual mode's complementary use with 'remove_contact'.

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 title 'Toggle auto-add for new contacts' and description clearly specify the verb 'Set' and resource (auto-add behavior for new contacts). It distinguishes itself from siblings like 'remove_contact' and 'import_contact' by mentioning their interplay.

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 a usage hint by pairing manual mode with 'remove_contact' for curated contact lists. However, it does not explicitly state when not to use the tool or list alternatives beyond that.

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