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

Annotations already carry readOnly/idempotent/non-destructive, so the description adds the useful operational detail that an empty list means no automation exists yet, plus the exact shape of each record. Pagination and filtering behavior are not mentioned.

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-loaded with purpose and scope, then next-step routing in one compact sentence. The field enumeration is slightly listy but each item earns its place given the missing output schema.

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 supplies the record shape, the empty-result semantics, and the natural follow-on tools. Nothing an agent needs to call this correctly is missing.

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 the baseline is 4. The description instead spends its words on the response fields (id, name, active, trigger, platforms, accountIds, totalRuns, updatedAt), which is useful given there is no output schema.

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 states a specific verb and resource ("List the chatbot automation flows") and even enumerates the flow types covered (comment-to-DM, keyword replies, welcome flows), so an agent knows exactly what is and is not returned. It also lists the returned fields, which reinforces the scope.

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?

It explicitly routes to the right follow-ups: get_automation for steps/runs, set_automation_active to toggle, get_automation_usage for runs per period, and create_automation_from_template to create. It does not, however, distinguish this from the sibling list_quick_automations or list_automation_templates, leaving a small ambiguity.

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