List DM automations

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description reinforces 'Read only' while adding useful domain context: the exact status values including on_but_over_plan_limit and the meaning of that state. Doesn't cover pagination or auth, but the annotated safety profile covers most of that burden.

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?

Front-loads the resource and packs field/status explanations into a single dense but purposeful passage. Slightly long and run-on, but nearly every clause conveys return-field meaning.

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 parameters and no output schema, the description compensates by naming the returned fields (id, name, status, trigger, steps, counts) and explaining status semantics. Complete enough to call correctly.

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?

Zero parameters, so the baseline of 4 applies. The description focuses entirely on return shape rather than inputs, which 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?

States a specific verb ('The workspace's DM automations') and resource, enumerating subtypes (comment to DM, keywords, story replies) that separate it from the sibling list_email_automations and from mutating siblings like create_automation/set_automation. An agent can identify this as the read-side listing without opening a schema.

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?

Explicitly says to 'Read it before switching one on or off,' pointing at the set/switch controls. Clear context for when to call, though it doesn't name the exact sibling (set_automation) or note exclusions.

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