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

With only false-valued annotations, the description carries the full burden of behavioral disclosure, and it delivers: no order/revenue booked, free first period, renewal behavior, reminder-only until account connection, existing members skipped, and return counts. This is richer than typical descriptions and gives an agent a realistic model of the tool's side effects.

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 structured front-to-back: what it does, when to use it, key behavioral effects, and the return shape. Every sentence adds information, and there is no filler or repetition.

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 6-parameter tool with no output schema and no helpful annotations, the description is unusually complete: it explains the core purpose, eligibility context, side-effect profile, default first-period behavior, how existing members are handled, and the exact return shape. There is little an agent needs to infer.

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 all parameters well. The description adds a little context about defaults and existing-member handling, but it does not meaningfully expand on parameter meaning beyond what the input schema provides.

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 clearly states a specific action — manually enrolling existing or off-platform people into a membership product without a payment — and gives a concrete backfill use case. This distinguishes it from sibling tools like neuron_add_group_members or neuron_checkout by emphasizing that no payment or order is booked.

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 description explicitly tells when to use the tool: backfill members who were already in the WhatsApp group before membership was switched on, so the renewal and eviction cycle applies to them. It does not name a specific alternative tool for paid enrollment, but the 'WITHOUT a payment' constraint makes the intended context clear.

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