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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description does add one genuinely useful behavioral fact not present in structured fields — the '(1 credit)' cost — but says nothing about pagination behaviour, result caps, or that a missing hashtag yields an empty set versus an error.

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 short fragments with zero filler and the resource stated up front; the credit cost is parenthetically appended where it is easy to scan. It is arguably under-specified rather than bloated, which is a completeness problem rather than a conciseness one.

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?

This is a simple two-parameter read tool with no output schema, so the bar is low and the description minimally suffices for invocation. However, with several near-identical hashtag/search siblings and no return-shape or pagination note, the definition leaves the agent guessing on selection and result volume.

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 both parameters (hashtag with optional '#', cursor from previous page) are already fully documented in the schema. The word 'Recent' hints at recency ordering but adds no syntax or format meaning beyond what the schema provides, so the 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 fragment 'Recent posts under a hashtag' names the resource, but supplies no verb and no scope limits (how many posts, what ordering, whose visibility). More critically, it does not distinguish itself from close siblings like instagram_search_hashtag or instagram_tagged_posts, so an agent must guess which hashtag-related tool to pick.

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 at all — no mention of when this is preferable to instagram_search_hashtag or instagram_search, and no prerequisites. The only guidance the agent gets comes from the tool name itself.

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