cm_get_journey_email_opens

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

Annotations already indicate readOnlyHint=true, so the description adds minimal behavioral info. It mentions 'paged', which hints at pagination, but does not detail return format, licensing, or rate limits. The schema covers pagination parameters, reducing the need for description.

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 single sentence that front-loads the verb and resource. No unnecessary words. Perfectly structured for quick scanning.

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?

Given the complexity (6 parameters, paging, no output schema), the description is minimally adequate. It identifies the tool's purpose but lacks details on return values or behavior beyond paging. Could be improved by stating what information the opens contain.

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 6 parameters. The description adds no additional information about parameters; it relies on the schema. Baseline 3 is appropriate since schema is already rich.

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?

Description clearly states the tool retrieves opens for a specific journey email, with paging. It uses specific verb 'Get' and resource 'journey email opens', distinguishing it from sibling tools like cm_get_journey_email_clicks or cm_get_journey_email_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?

No explicit guidance on when to use this tool versus alternatives (e.g., cm_get_journey_email_recipients). The name implies the use case, but prerequisites (e.g., requiring a journey email ID) are not mentioned. However, the schema indicates the required emailId parameter.

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