get_hashtag_media

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

No annotations are present, so the description carries the behavioral disclosure burden. It surfaces the per-account rate limit, the prior lookup requirement, and the edge/limit constraints. It does not mention pagination or default-account behavior, but those are partly addressable via the existing output schema.

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?

Two dense, well-organized blocks with no filler. The first sentence defines the operation, the second gives parameter constraints, and the final sentence provides prerequisite and quota context. Every sentence earns its place.

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 4-parameter tool with no annotations, the description covers purpose, main parameter semantics, a prerequisite, and quota awareness. The main gap is the unexplained account parameter. Since an output schema exists, the lack of return-value detail is acceptable.

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 0%, so the description must compensate. It explains edge values, the limit range, and where hashtag_id comes from. However, the optional 'account' parameter is entirely unexplained—an agent does not know what value format it expects or what null means.

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: 'Recent or top media for a hashtag id.' It also names the edge variants and limit range, making the tool's function immediately identifiable. The note about obtaining hashtag_id from search_hashtag separates it from that sibling tool.

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 gives a prerequisite: 'Get the hashtag_id from search_hashtag first.' It also warns about Meta's 30-unique-hashtags per-7-days limit, which helps an agent decide when this call is appropriate. It does not enumerate alternatives like list_media or get_media, so exclusions are not fully explicit.

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