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

With no annotations, the description carries the full burden, and it does disclose two useful operational facts: a cost of 1 credit and the Authorization: Bearer <api_key> requirement. It adds pagination and author-identity context, but says nothing about rate limits, private/deleted media behavior, or error handling.

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 core clause is front-loaded and short, but there is a doubled period typo ('pagination..') and the boilerplate 'Platform=instagram resource=comments' restates the tool name, adding length without information.

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 usefully summarizes the return content (author identity) and pagination behavior, plus cost and auth. For a three-parameter read tool this is nearly complete, with only error and edge-case behavior left uncovered.

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 the schema already documents media_id, cursor, and sorting including defaults and examples. The description only gestures at pagination ('cursor') and adds no syntax or format detail beyond the schema, so baseline 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?

The description states a specific verb and resource: fetching public comments for a media id, including author identity and pagination. It is clear what the tool returns, though it never names how it differs from sibling endpoints like instagram_post or instagram_detailed.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. The agent must infer from the tool name alone that this is the comments endpoint rather than the post or user endpoint, which is thin routing guidance in a 40-sibling namespace.

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