Marketing automation and its stats

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

Annotations already carry readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuine behavioral value by enumerating exactly which metrics are returned (journey starts, open/click rates, donations, objective reached, unsubscribes, SMS delivery, jumps) and by noting the month-range scoping option, none of which are in the annotations.

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?

Two efficient sentences: the purpose and metric enumeration lead, the optional month scoping follows. The metric list is long but earns its place since there is no output schema to describe return values.

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 no output schema, the description correctly shoulders the burden of describing what is returned via its metric enumeration. The only gap is the undocumented include_stats parameter, which is missing from both schema description and prose.

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 75%, so most parameters (automation_id, start_month, end_month with YYYYMM pattern and format) are already documented in the schema. The description restates the month-range concept but adds no syntax or constraints beyond the schema, and it never explains the undocumented include_stats parameter.

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?

States a specific verb and resource (retrieve one marketing automation) and enumerates the statistics it returns, so the purpose is clear. It implicitly distinguishes itself from the sibling list_marketing_automations by the singular 'One marketing automation', but never names that sibling explicitly.

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 notes the optional month-range limiting, which is implied usage guidance. However, it offers no explicit when-to-use/when-not-to-use, does not say to call list_marketing_automations first to obtain the ID, and does not address the include_stats toggle.

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