Create newsletter list subscription

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, but the description adds context the annotations do not: it mutates account state, requires an explicit confirm=true gate, and demands the newsletter_lists:write OAuth scope. That is real added value. It stops short of describing reversibility or error behavior.

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?

Three short sentences, front-loaded with the action and then the two constraints (confirm gate, OAuth scope). No filler. "Changes account state" is slightly vague but the sentence still earns its place as a mutation warning.

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 destructive 8-parameter tool with a nested payload object and no output schema, the description covers the essentials an agent needs before invoking: state mutation, the confirm gate, and the required OAuth scope. It omits interaction rules between payload/payload_file/body flags and any return information, but those gaps are largely handled by the 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?

Schema description coverage is 100%, so all 8 parameters, including the nested payload/payload_file alternates and the subscription_id-or-email rule, are already documented in the schema. The description only echoes the confirm parameter, adding no syntax or format meaning beyond the structured data, so the baseline 3 applies.

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 and resource ("Create newsletter list subscription"), which is clear enough to distinguish it from list/get/update newsletter-list-subscription siblings. It does not, however, contrast itself with the closely related create_subscription or create_bulk_subscription tools, so an agent must infer the boundary.

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 line "requires confirm=true for the user-requested action" gives a concrete usage rule for the confirm flag, which is genuinely useful. But there is no guidance on when to choose this tool over create_subscription, update_newsletter_list_subscription, or the bulk variants, and no explicit exclusions.

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