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

Beyond the readOnlyHint/openWorldHint annotations, it discloses two operationally important traits: results are single-page with no cursor, and each call costs 1 credit. It also warns that follower counts are a thinner summary than the full profile. No auth or rate-limit detail, but the added context is meaningful.

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 the core purpose, followed by the useful caveats. Each sentence carries information, though the fragment 'Accounts matching a query, as unified Creators' reads awkwardly.

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 should carry return-value burden; it only hints that results contain thin follower counts and are paginated to one page. It does not say the result is a list of accounts or what fields each carries, leaving the response shape underspecified.

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 50%: 'query' is documented in the schema, but 'cache_max_age' is undocumented in both schema and description, and the description never mentions caching behavior. The description's 'Accounts matching a query' adds no syntax or format detail beyond the schema, so the coverage gap is not compensated.

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 and resource ('Search accounts') and adds that results are returned as 'unified Creators', which tells the agent the shape of the result. It does not distinguish this from the sibling instagram_search, so an agent cannot tell which of the two search surfaces to pick from the text alone.

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?

Explicitly routes the agent to instagram_profile ('Fetch that for one account you care about') when detailed follower counts are needed, and states the one-page/no-cursor limitation. Missing is any guidance on when to prefer instagram_search vs this tool.

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