Spotify Play Count & Monthly Listeners Scraper

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

Beyond the read-only and open-world annotations, it explains that each invocation starts an Apify Actor run through the hosted gateway, requires the caller's APIFY_TOKEN, and uses their Apify account. It also discloses the public-data-only behavior, output rows and paging IDs, daily-tracking warm-up behavior, and documentation link.

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?

The labeled 'When to use,' 'Returns,' and 'Behavior' paragraphs make the detailed description easy to scan, and the core capability is front-loaded. However, the opening repeats the title and the first two paragraphs overlap substantially in listing capabilities and metrics.

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 hosted scraper with four parameters and no output schema, the definition covers inputs, outputs, authentication, run behavior, read-only scope, tracking caveats, exclusions, and documentation. Together with the fully described schema, it leaves no material gap likely to impede correct selection or invocation.

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 structured fields already document all four parameters well. The description reinforces supported target types and daily-stream history behavior but adds little beyond the schema, and it provides no extra invocation detail for maxTracksPerTarget or includeArtistAlbums.

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 the resource and operation precisely: scraping track play counts from Spotify track, album, artist, or playlist targets, with artist listeners, followers, rank, and top cities also available. It further distinguishes optional daily-stream history from the core play-count results.

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?

An explicit 'When to use' section gives concrete use cases: release tracking, playlist checks, and artist comparisons. It also supplies clear exclusions, stating that the tool is not for private Spotify for Artists data or royalties.

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