Track part

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful behavioral content by explaining what each part returns, but says nothing about auth needs, missing/private tracks, rate limits, or response shape — notable given there is no 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?

A single sentence, front-loaded with the resource and then the enumerated variants — every clause carries information and nothing is repeated from structured fields.

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 read-only, three-required-param tool with no output schema, the description covers what each part yields but not what the response looks like or how it relates to get_track. Adequate to invoke, thin on what to expect back.

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 67%: author and track have permalink examples, but the part enum has no per-value description in the schema. The description compensates by defining all five enum values, which is exactly the gap the schema leaves.

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 (a part of one track) and enumerates all five part values with a gloss for each (chapters/tracklist, AI transcript, similar tracks, emoji reactions, comments), so an agent knows exactly what content comes back. It stops short of an explicit verb or a direct contrast with the sibling get_track, leaving the read-vs-detail relationship implicit.

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 statement of when to reach for this tool versus get_track, and no prerequisites (author + track permalinks are both required). The only guidance is the implicit 'more about one track' framing, which is not enough to route between siblings.

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