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

Annotations already cover read-only, idempotent, non-destructive, so the safety bar is met. The description adds genuinely non-obvious behavior: the 100-track cap, that lifetime play counts are attached, and that subsequent pages omit metadata and consume one request each — useful for planning request budgets.

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 tight sentences with zero filler. The payload content is front-loaded, the pagination rule follows. Every clause carries information an agent needs.

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?

There is no output schema, so the description carries the return-value burden and does so — it lists the metadata fields, the track slice, play counts, and the `next_offset` control field. Nothing essential to correct invocation is missing.

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 100%, so the baseline is 3. The description goes beyond the schema by tying `offset`/`limit` to a paging loop driven by a `next_offset` value returned in the answer, which adds interpretive meaning the schema alone doesn't convey.

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 names the resource and enumerates exactly what comes back — name, owner, followers, description, plus a bounded track slice with lifetime play counts — so the agent knows this is a playlist-metadata-plus-track-page tool. It does not explicitly contrast with siblings like `get_tracks` or `get_album`, but the scope is unambiguous on its own.

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?

It gives concrete operational guidance: use `next_offset` from the response to page, and later pages skip metadata and cost one request. That tells the agent how to iterate. It stops short of stating when to prefer this over `get_tracks` or `search`, so no explicit alternative routing.

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