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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that results are user-generated Instagram content to be treated as untrusted input — a real safety caveat — but says nothing about how popularity is ranked, required auth, rate limits, or pagination behavior.

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, front-loaded sentences with no waste: purpose first, safety caveat second. It could be slightly tighter and would benefit from adding the ranking/selection context in the same space.

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 one-parameter, no-annotation, no-output-schema tool the description is adequate: purpose plus a trust warning. It still omits the ranking semantics for "top" and any routing against search_tracks, leaving an agent to infer both.

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% and the single required `limit` parameter is fully documented in the schema (1-100). The description adds no additional parameter semantics, which matches the baseline of 3 when the schema does the heavy lifting.

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+resource ("Get popular music tracks"), which is clear and distinct from search_tracks by implying a ranked/popularity ordering. However it never names the sibling it contrasts with (search_tracks, get_track_by_id), so an agent must infer the distinction from the word "top".

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 or when-not-to-use guidance. With siblings like search_tracks and get_track_by_id available, the description should say when a ranked top-list is preferred over a search or a by-id lookup, and it does not.

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