batch_subscribe

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

No annotations provided, so description carries full burden. It discloses side effect (double opt-in email for pending members), synchronous nature, authentication, concurrency limits, and respect for read-only/dry-run modes. The return structure includes error handling details.

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 well-structured with distinct sections: purpose, usage guidelines, side effects, and an 'Args' bullet list for parameters. Each sentence adds value without redundancy. It is concise yet comprehensive.

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?

Given the tool's complexity (batch subscription with up to 500 members), the description covers all necessary aspects: purpose, when to use, parameters with details, side effects, authentication, concurrency, and return structure. No gaps remain.

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?

With 0% schema description coverage, the description adds full meaning for all three parameters: list_id (format, example, source), members_json (max 500, required fields, optional fields), update_existing (default, behavior). This compensates completely for the schema's lack of descriptions.

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 the tool adds or updates up to 500 members in a single synchronous request, with specific verb and resource. It also distinguishes from siblings by mentioning batch_subscribe for 2-500 members versus add_member/update_member for single and create_batch for larger imports.

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?

Explicitly provides when to use (bulk operations, 2-500 members) and when not (single members, imports >500) with named alternatives (add_member, update_member, create_batch). Also mentions authentication via API key and max 10 concurrent requests.

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