cm_get_bounced_subscribers

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

Annotations already declare readOnlyHint=true, consistent with a read operation. The description adds 'paged', indicating pagination support, but does not outline other behaviors like error handling, rate limits, or data format. Adequate but not rich.

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?

Extremely concise and front-loaded. Every word serves a purpose: 'Get', 'list's bounced subscribers', 'paged'. No fluff 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?

With 6 parameters and no output schema, the description is minimal. It does not explain return structure, error cases, or field details. Adequate for a simple data retrieval tool but could include more context.

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 each parameter already described. The tool description does not add new semantic information beyond the schema; it only mentions 'paged' which aligns with page/pagesize params. Baseline 3 for high schema coverage.

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 bounced subscribers for a list with pagination. It uses a specific verb ('Get') and resource ('bounced subscribers'), distinguishing it from siblings like cm_get_active_subscribers or cm_get_unsubscribed_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?

No explicit guidance on when to use this tool versus alternatives (e.g., cm_get_active_subscribers). The purpose is clear, but usage context is merely implied by the tool name and sibling list; no when-not or exclusion criteria.

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