Instagram Post Stats API

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

Annotations already provide readOnlyHint and openWorldHint, and the description adds valuable behavior: credit cost on live reads, free cache hits, return shape ('one object'), platform-specific field naming, and explicit exclusion of private or profile data. No contradiction.

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?

Four short, front-loaded sentences with no wasted words. Each sentence adds a distinct piece of information: scope, return shape, cost/cache behavior, and public-data restrictions.

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?

For a simple two-parameter read-only tool, the description covers purpose, parameter behavior, return shape, cost/cache semantics, and data boundaries. Nothing essential for invoking it 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?

Schema coverage is 100% and both parameters (url and cache) already have explanatory descriptions. The tool description adds no parameter-specific meaning beyond the schema, so the baseline of 3 applies.

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 clearly that it returns likes, comments, and views for a public Instagram post or reel as a single object. This distinguishes it from sibling profile/posts/stats tools by resource type and data 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?

Provides clear context: use it for public posts/reels, not for bios, contact details, or login-walled data, and it explains the cache/live-cost tradeoff. It does not explicitly name sibling alternatives, but the boundary conditions make the appropriate use reasonably clear.

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