Hashtag media — top or recent

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

No annotations are provided, and the description only implies GET behavior via the endpoint string. It does not disclose pagination behavior (auto_paginate, max_pages), rate limits, or auth details beyond user_id. Minimal transparency for a tool with 7 parameters.

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 very short (one sentence), but it is underspecified rather than efficiently concise. It could include key behavioral details without being much longer.

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 tool with 7 parameters, 3 required, no output schema, and high complexity (pagination, enum kind), the description is severely incomplete. It lacks any explanation of return values, pagination logic, or the difference between top and recent media.

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 0%, so the description must compensate. It only mentions hashtag_id (via the path) and user_id, and indirectly kind ('top_media or recent_media'). It adds no meaning for fields, limit, auto_paginate, or max_pages, leaving 5 of 7 parameters undocumented.

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 'GET /{hashtag_id}/top_media or /{hashtag_id}/recent_media', which clearly identifies the tool as retrieving hashtag media for top or recent categories. It distinguishes from siblings like ig_hashtag_search, but does not explain the difference between top and recent media.

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 notes that 'user_id is required by Meta', providing a context-specific requirement. However, it offers no guidance on when to use this tool versus alternatives (e.g., ig_media_list), nor any exclusions or complementary tools.

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