cm_get_active_subscribers

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

Annotations note readOnlyHint=true, and the description confirms a read-only 'Get' operation. It adds behavioral context about paging and optional date filtering, which is consistent with annotations. No contradictions.

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 a single, concise sentence that front-loads the key purpose and optional features. No wasted words.

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?

With no output schema and 6 parameters, the description is brief. It highlights date and paging but omits details on ordering fields and result format. Adequate but with gaps.

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 100% with all parameters described. The description adds minimal value beyond the schema, only reiterating that paging and date filtering are supported. Baseline of 3 is appropriate.

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 retrieves active subscribers from a specific list, with pagination and optional date filter. It distinguishes from siblings like 'cm_get_subscriber' (single subscriber) and 'cm_get_deleted_subscribers'.

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 implies usage for retrieving active subscribers with paging and date filter, but provides no explicit guidance on when to use this tool versus alternatives (e.g., 'cm_get_subscriber' for a single subscriber, or 'cm_get_list_stats' for aggregate data).

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