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

With no annotations, the description carries a full burden for behavioral disclosure. It does reveal that opting out suppresses notices conservatively and requires no external identity proof, but it omits important behaviors like persistence, reversibility, versioning semantics, and idempotency implications.

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 two sentences with clear front-loading of the action. Both sentences earn their place, one stating the purpose and the other adding behavioral context.

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 nested preference object, mandatory expectedVersion, and idempotencyKey, the description is far too sparse. An agent cannot safely construct a correct call without understanding versioning and idempotency semantics, which the description does not explain.

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 adds no meaning for either parameter. idempotencyKey and expectedVersion are never referenced, leaving the agent unable to infer their values or purpose.

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 states a clear verb and resource: set your contact preference. It is distinct from most sibling tools, but it does not explicitly differentiate it from notification-related tools like subscribe or suppress_outreach_subject.

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?

No guidance is given on when to use this tool versus alternatives such as subscribe or suppress_outreach_subject, nor are prerequisites or exclusions mentioned. The context is only implied by the tool name and the brief opt-out note.

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