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

Annotations already declare destructiveHint=true and openWorldHint=true, but the description adds genuinely useful behavior beyond them: contacts are auto-created in the CRM if missing, and existing enrollments/suppressed numbers are silently skipped. It does not disclose volume limits or what an agent should expect per-phone results for a bulk call.

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?

A single compact paragraph with the most important information (what it does, identifier format, auto-creation, skip rules) front-loaded after the section header. Efficient, though the emoji/header convention is decorative rather than informative.

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 bulk, non-read-only mutation with no output schema, the description never says what comes back (e.g. how many were enrolled versus skipped and why). It also does not surface the admin-only restriction on target_user_id, which lives only in the schema. Adequate but with a real gap for an agent that needs to interpret results.

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 five parameters are already documented. The description only restates the phone format already in the schema and adds nothing about contact_names pairing, start_at semantics, or the admin-only target_user_id override. 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?

The description states a precise verb+resource ('Matricula contatos em uma cadência de prospecção'), defines the identifier used (phone in international format), and clarifies the implicit side effect of creating the contact in the CRM. This distinguishes it from siblings like list_enrollments, count_enrollments and manage_enrollment.

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 makes clear when the tool applies (enrolling contacts in a multi-touch sequence) and states the exclusion rules: contacts already active/paused or on the LGPD suppression list are ignored. It does not explicitly name alternative tools (e.g. update_contact for existing records or manage_enrollment for status changes), so it stops short of full routing guidance.

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