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

Annotations already cover the safety profile (readOnlyHint, openWorldHint, destructiveHint false). The description adds real value beyond them: the required posts:read scope, the human-in-the-loop constraint that an agent cannot connect an account because consent belongs to Instagram, and a sketch of the returned rule structure. It does not mention pagination, result limits, or empty-result behavior.

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 tight sentences, front-loaded with what is read, then the posts: true behavior, then the caveat about connecting accounts. Every sentence is useful, though the Hub-connection aside is slightly tangential to invoking the tool.

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 return-shape burden and does a fair job (accounts, rules with keywords/reply variants/private message, recent answers). Missing pagination and result-volume details keep it from being fully complete for a potentially multi-account listing tool.

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%, so both parameters are already documented inline. The description restates them ('Set posts: true to also list...', 'needed with posts when several are connected') with only marginal additions such as 'the ids a rule can listen on'. Baseline 3 applies when the schema carries the parameter semantics.

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 (Reads) and a precisely scoped resource: the connected Instagram accounts for auto-replies, their rules, and recent answers. It goes further than a label by outlining what a rule contains (keywords, public reply variants, optional private message), so an agent knows exactly what this tool surfaces versus the create/update/delete_autoreply 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 usage guidance: set posts: true to include recent posts and the ids a rule can listen on. It also states a permission prerequisite (requires posts:read) and explains the fallback when nothing is returned (a human connects the account in Hub). No sibling alternative is named, and there are no explicit when-not-to-use conditions, so it stops short of a 5.

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