instagram_get_followers

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

The description adds significant behavioral context beyond the annotations: performance characteristics (slow for thousands), rate-limit risk, and a directive to minimize the amount. It also specifies the ordering and the return structure. The annotations already declare read-only/idempotent, so the description enriches rather than repeats them. No contradictions.

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 well-structured with a one-sentence purpose, a focused usage warning, then clearly labeled Args and Returns sections. It is compact, front-loaded with the core purpose, and every sentence earns its place. No fluff.

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?

The description covers the tool's scope, limitations, performance trade-offs, and return fields. Combined with the rich input schema and annotations (read-only, idempotent), it gives an agent everything needed to call the tool correctly. Nothing essential 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?

Schema coverage is 100%, and the schema descriptions for each parameter are more detailed than the Args section in the description (e.g., amount includes 'Large values take minutes and risk rate limits'). The description's param mentions add little beyond what the schema already provides. 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 states a specific verb ('List') and resource ('accounts that follow a user') plus an ordering detail ('newest follower first'). This clearly distinguishes it from the sibling instagram_get_following, which would list accounts a user follows. The purpose is unambiguous.

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 explicitly states when the tool works (own account, public accounts, private accounts you follow) and includes a strong recommendation to request the smallest number needed to avoid rate limiting. It does not name alternative tools like instagram_get_following, but the purpose statement makes the distinction obvious. The guidance is clear and actionable.

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