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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description adds real context the annotations don't: platform restriction to Instagram/Facebook, an admin-only authorization requirement, and the fact that the response includes accountId values for use in creation.

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 sentences, front-loaded with the action and resource, then the supporting mechanism and constraints. No filler or repetition of the title, and each clause (platform limit, admin gate, accountId return) carries information.

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 and no parameters, the description carries the burden and does well: it defines the automation concept, platform scope, permission requirement, and a key part of the return payload. It does not mention pagination or result limits, which is a minor remaining gap for a list operation.

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 of 4 applies. The description correctly focuses on scope and return content rather than inventing parameter detail.

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 (List) and resource (the account's comment→DM automations), then explains the underlying mechanism (keyword comment on a post or story reply triggers an automatic DM and optional public reply). The 'List' verb cleanly separates it from the create/update/delete_comment_automation siblings.

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?

Gives concrete context: it's Instagram and Facebook only, it's admin-only, and it also surfaces the accountId values needed when creating an automation — which implicitly positions it as the prerequisite read before create_comment_automation. It stops short of an explicit when-to-use vs. alternatives statement, so it isn't a full 5.

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