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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds real behavioral context: ranking can be by engagement (likes, comments, views) or recency, and results are verified media URLs plus performance notes. Minor gap: no parameter actually controls the engagement-vs-recency choice, so that behavior is ambiguous.

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 tightly packed sentences with zero filler; the identification of the resource and its ranking come first, and the consumption context comes last.

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 previews the return payload (media URLs, performance notes) and the downstream consumer. For a two-parameter read tool this is nearly enough, though it never explains what happens when no published media exists or how 'top-performing' is defined relative to recency.

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 'limit' and 'platform' are fully documented at the schema level. The description adds nothing about parameter semantics, which is the expected baseline when the schema does the work.

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 ('Fetch') and a precisely scoped resource ('top-performing published post images and videos'), with the ranking dimension named. It implicitly separates itself from get_top_posts by restricting to media assets, though it never names that sibling explicitly.

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?

Gives a downstream context ('to present in show_image_carousel'), which implies when to reach for it, but offers no explicit when-not guidance or mention of the close alternative get_top_posts. Usage is inferable rather than stated.

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