cm_import_subscribers

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

The description only says 'bulk-add', implying mutation, but no annotations (e.g., destructiveHint) are provided. It does not disclose behavioral traits like handling of duplicates, overwriting behaviors, or any side effects. With no annotations, the description should provide more context but fails to do so.

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 very concise (one sentence) but under-specified. Given the tool has 5 parameters and a nested object, the description is too short to be effective. It sacrifices completeness for brevity, making it inadequate.

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?

The description is incomplete given the tool complexity. It lacks information on behavior for optional parameters (like QueueSubscriptionBasedAutoResponders), return values (no output schema), and how to handle results. The sibling tool list shows many related operations, but no guidance on when to import vs add or update.

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 60%, but the description adds no extra meaning beyond what is in the schema. For example, it does not explain what 'Resubscribe' does or how the 'Subscribers' array structure works. The description is too brief to add value to the parameter documentation.

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 action (bulk-add) and the resource (many subscribers to a list) and distinguishes itself from sibling tools like cm_add_subscriber (single subscriber) and cm_update_subscriber (update). It is specific and unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., cm_add_subscriber for single adds, cm_update_subscriber for updates). The description does not mention prerequisites or context for bulk importing.

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