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

The annotations already establish that this is a read-only, non-destructive, open-world operation. The description adds useful semantic context about what the rules do and what status information is shown, but it does not cover pagination, authorization requirements, or other operational behavior beyond 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?

The description is a single well-formed sentence with no wasted wording. It front-loads the core resource and packs trigger conditions, grouping, and status into a compact statement.

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 low-complexity read-only list tool with one optional parameter and no output schema, the description gives enough context about what is returned: rules, trigger type, account/post scope, and status. It could still be more complete by clarifying behavior when brand_id is omitted or whether pagination applies.

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 description coverage is 100%, and the only parameter, brand_id, is documented directly in the schema with guidance from list_brands and how to handle ambiguous user naming. The description does not add meaning beyond the schema for this parameter, so the baseline 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 identifies the resource: DM automation rules with keyword-comment or story-reply triggers, grouped by account and post, including status. It does not use an explicit list/view verb in the description itself, but the title and tool name make the purpose clear and the domain is distinguishable from sibling tools.

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 explains what these rules are but gives no explicit guidance on when to use this tool versus alternatives such as save_dm_automation, list_comment_bots, or start_automation_setup. The reading use case is implied, but there is no when-to-use or when-not-to-use guidance.

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