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

Annotations already mark the tool as read-only and non-destructive. The description adds meaningful behavioral detail beyond those annotations: results are paginated, and if the library is empty the tool supplies guidance for requesting audio files or Spotify/SoundCloud links. This gives the agent useful expectations about non-standard empty-library 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 sentences, no filler. The primary action is front-loaded, the returned metrics are named, and the pagination plus empty-library behavior are conveyed economically. Every sentence contributes useful information.

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 simple read-only list tool with a 100%-documented schema and an output schema, the description is complete. It covers the scope, the data returned, pagination behavior, and the notable empty-library edge case. No critical context appears 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 description coverage is 100%, so the schema fully documents both parameters (limit and cursor). The description's mention of 'paginated results' reinforces the limit/cursor semantics but does not add new parameter-level meaning beyond what the schema already states.

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 identifies a specific verb ('List'), a specific resource ('tracks'), and the scope ('in the current company'), plus the distinguishing data points (play, download, and view counts). This makes it clearly distinguishable from siblings like get_track_details or get_track_analytics by framing the operation as a list-level read.

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?

The description gives clear usage context: it is for listing tracks at the company level, with counts and pagination. It does not explicitly name alternatives or exclusion criteria, but the listing scope and count-based output make it easy for an agent to choose this over detail- or analytics-focused siblings.

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