cm_get_journey_email_unsubscribes

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

The description only says 'Get', which aligns with the readOnlyHint annotation. However, it adds no extra behavioral context beyond the annotation, such as authentication requirements, rate limits, error behavior, or result structure. For a read-only tool, the description should ideally mention expected output format or data freshness.

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, well-structured sentence that is front-loaded with the core action and includes the important qualifier '(paged)'. Every word is meaningful; no unnecessary content.

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?

There is no output schema, so the agent must infer the return format. The description does not describe what fields an unsubscribe record contains, how pagination works (e.g., total count, next page token), or any constraints. Given the simple purpose, more detail on the output would improve completeness.

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?

The schema coverage is 100%, so all parameters have descriptions in the input schema. The tool description does not add any additional meaning or provide examples beyond what the schema already offers. Baseline score 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 verb 'Get' and the resource 'unsubscribes for a specific journey email', and includes the qualifier '(paged)' to indicate paginated results. This distinguishes it from sibling tools like cm_get_journey_email_bounces 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?

The description implies usage for fetching unsubscribes of a journey email, but does not explicitly state when to use this tool versus related tools (e.g., cm_get_journey_email_bounces, cm_get_journey_email_opens). No exclusions or alternatives are mentioned.

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