get_journey_email_bounces

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

With no annotations, the description bears full responsibility for disclosing traits. It only mentions 'paginated list' but does not state that the tool is read-only, what constitutes a bounce, or any prerequisites like authentication or rate limits. Information is minimal.

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?

A single sentence of 10 words that front-loads the verb and resource. No unnecessary words or redundancy. Ideal conciseness.

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 tool with 3 parameters and no output schema, the description lacks context about the meaning of 'bounces', the output format, error handling, and required permissions. It is insufficient for an agent to fully understand usage without additional knowledge.

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 descriptions for all three parameters. The tool description adds no further meaning beyond 'paginated', which is already implied by the page and page_size parameters. 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 action (Get), the resource (bounces for a journey email), and includes the key differentiator 'paginated', which distinguishes it from siblings like get_journey_email_clicks or get_journey_email_opens.

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 on when to use this tool versus alternatives such as get_journey_email_clicks or get_journey_email_unsubscribes. The differentiation relies solely on the tool name, and no context is provided for selecting this over other similar tools.

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