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

Annotations only say readOnlyHint=false, destructiveHint=false, idempotentHint=false; the description adds the crucial behavioral fact that nothing is enrolled until confirm_action runs, which tells the agent the call is non-committal despite the write-flavored name. It does not describe what the call returns (a preview? a token to pass to confirm_action?) or how long a prepared enrollment stays valid.

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 short sentences with the staging semantics front-loaded and the gating condition second. No filler, no restatement of the tool name.

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 no-output-schema, three-parameter staging tool, the description covers the essential flow an agent needs to avoid double-enrolling someone. Gaps remain around parameter relationships and what to do with the result, but the core contract is conveyed.

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 0% for three parameters, so the description must carry the load. It hints that 'a list or specific people' correspond to list_id vs prospect_ids, implying they are alternatives, but it says nothing about formats, whether they are mutually exclusive, or that campaign_id is required.

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 names a specific action (preparing to add a list or specific people to a campaign) and correctly reframes the misleading 'enroll' name as a staging step. It implicitly separates itself from confirm_action, which handles the actual enrollment, though it doesn't say how it relates to sibling tools like list_lists or search_prospects that would supply the inputs.

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 clearly states the two-step flow: call this to prepare, then confirm_action once the user agrees in chat. That gives an explicit when-to-use and names the follow-up tool, but it offers no exclusion guidance (e.g., whether it can be called repeatedly, or what to do if the user declines).

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