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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds real value on top by disclosing the non-archived filter, the available states (On, Paused, Draft), and the non-obvious row-multiplication behavior (one row per account sharing a group_id). It doesn't discuss ordering, size limits, or empty-account behavior, which keeps it out of 5 territory.

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 dense sentences, front-loaded with the scope constraint ('not archived'), then the row shape, then the edge case that would otherwise confuse an agent. No filler or restatement of the title.

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 carries the burden of describing returns, and it does so field-by-field plus the group_id grouping rule. What's missing is minor: ordering, result-size expectations, and whether an empty result is indistinguishable from no automations.

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 per the rubric the baseline is 4; there is no parameter semantics to document or misdocument. No corrective information is needed here.

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+resource ('Every Instagram automation on this account that is not archived') and enumerates the fields returned per row, so the agent knows exactly what this produces. It does not explicitly differentiate itself from the sibling list_automation_templates, which is the one plausible confusion point, so it stops short of a 5.

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?

Usage is only implied: the agent can infer this is the way to enumerate existing (non-archived) automations, and the archived exclusion narrows the scope. There is no explicit when-to-use statement, no condition distinguishing it from list_automation_templates, and no mention of what to do next (get_automation_usage, pause_automation).

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