cm_get_journey_email_bounces

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

The description 'Get bounces (paged)' aligns with readOnlyHint and adds the paging behavior. However, it does not disclose other traits like filtering behavior, error handling, or that it only returns records for the specific emailId. With annotations already marking it read-only, the description adds minimal extra transparency.

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, clear sentence with no filler. It is front-loaded with the key action and resource. Every word earns its place.

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 paged read operation with no output schema, the description is adequate but lacks details on the return format, default sorting, or what constitutes a bounce record. It meets minimum viability but could be more complete.

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%, so the parameters are well-documented. The description mentions 'paged' but does not add meaning beyond the schema for parameters like date, page, or orderfield. It relies on the schema's 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 'Get bounces for a specific journey email (paged).' It specifies the action (Get), the resource (bounces for a journey email), and includes the paging aspect, distinguishing it from siblings like cm_get_campaign_bounces.

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 journey emails but does not provide explicit guidance on when to use this tool versus alternatives like cm_get_campaign_bounces or cm_get_bounced_subscribers. No exclusions or specific context are given.

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