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

Annotations already declare destructiveHint=true and idempotentHint=false, so safety is covered. The description adds a genuine side effect not in the annotations: turning double opt-in off also turns enrichment off, which is exactly the kind of hidden coupling an agent needs before calling.

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, no filler, with the core action front-loaded and the dependency caveat immediately after. Every clause carries information.

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 mutation tool with no output schema but with annotations covering the safety profile, the description covers the semantic behavior well. It leaves unstated whether the change is reversible or how it affects already-collected contacts, which is a minor remaining gap.

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 only 50%; the two bare booleans (enrich, doubleOptIn) have no schema descriptions. The description compensates by explaining what enrichment is, what triggers it, and how doubleOptIn interacts with enrich, which meaningfully disambiguates both undocumented parameters.

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?

States a specific verb (turns on/off) and resource scope (double opt-in / enrichment for one form), which is precise enough to distinguish from workspace-wide siblings like update_enrichment_settings. It does not name or exclude those siblings explicitly, so it stops short of a 5.

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 second sentence supplies real operating conditions: enrichment only applies to HelpWell confirmed sign-ups and depends on double opt-in being enabled. That tells the agent when this setting is meaningful, but there is no explicit guidance on choosing this tool over update_enrichment_settings or list_form_settings.

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