Add a subscriber to workflow.

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true. The description adds genuine context beyond that — the repetition prerequisite and the abandoned-cart restriction — which the agent cannot infer from the annotations. It still doesn't say what happens on rejection (error vs. silent no-op).

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 content is short, but it is wrapped in raw HTML (<br><b>, <ul>) with no leading purpose sentence, so the reader hits formatting markup before any substance. It is efficient in word count but poorly front-loaded.

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, non-idempotent mutation with 7 parameters and a nested payload object, the description covers key preconditions but omits error behavior and confirmation semantics (why confirm must be true). It is adequate but leaves real gaps for an agent invoking a write operation.

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 id/email mutual dependency, payload, payload_file, account, and confirm. The description adds no parameter-level meaning, which is acceptable but not additive — baseline 3.

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 tool name and title state a specific verb+resource ('add_subscriber_to_workflow'), which an agent can distinguish from the sibling remove_subscriber_from_workflow. However, the description body itself never states what the tool does — it opens directly with 'Notes:' constraints, so the purpose rests entirely on the name/title rather than the prose.

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?

It gives concrete when-not conditions: subscribers can only be re-added after completing the workflow and only if 'Allow repeat subscribers' is enabled, and abandoned cart workflows are excluded. No alternative tool is named, but the exclusion criteria are explicit and actionable.

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