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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so 'Read only' is largely redundant. The description earns credit elsewhere: it explains the non-obvious on_but_over_plan_limit status value (plan runs fewer automations than are switched on) and discloses the shape of the returned payload, including engagement counts. It does not mention pagination, result-size limits, or ordering, which is the main remaining gap for a list endpoint.

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?

Three sentences, front-loaded with the read-only constraint and the resource, and the long field enumeration is at least grouped in a single parenthetical. The middle sentence is dense and slightly run-on with its nested parentheses, but no sentence is filler.

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 zero-parameter read tool with annotations and no output schema, the description carries most of the burden and does so by describing the returned fields and the meaning of the status values. Pagination and result-set limits are the only material omissions an agent might need before calling it.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline applies. Nothing in the description invents or misdescribes an argument.

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 names a specific resource (the workspace's DM automations) and enumerates what each record carries — id, name, status, trigger, step count and metrics — so an agent knows exactly what this returns. It doesn't explicitly contrast itself with the sibling postfjord_list_email_automations, leaving the channel distinction to be inferred from the word 'DM'.

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 final sentence gives an explicit when-to-use rule: 'Read it before switching one on or off,' making this the lookup step before a status mutation. There is no when-not guidance and no named alternative, but the usage context is clear rather than implied.

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