artist_representation_census

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

With no annotations present, the description carries the full behavioral burden. It explicitly labels the tool 'Read-only,' which is a critical non-mutation trait. It also clarifies the algorithmic behavior that credited artists are counted for each saved track they appear on, not merely artists you follow or own albums by.

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 entire description is one tight, front-loaded sentence. It defines the resource, the operation, the ranking criterion, and the read-only nature without any filler or redundant restatement.

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 aggregation tool, the description plus the fully documented schema is largely sufficient. It explains the core output concept, and the schema covers caps and response formats. It could be more complete by noting how multi-artist tracks affect counts or what the returned rows look like, but these are not blocking gaps.

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 all four parameters are already documented in the schema. The description adds only a small reinforcement of 'top N' aligning with top_n, but it does not otherwise deepen meaning beyond the schema. Baseline of 3 is appropriate.

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 clearly states the operation: censusing saved tracks and ranking credited artists by how many saved tracks they appear on. The verb 'rank' and the scope 'your saved tracks' are specific. It does not explicitly differentiate from near-neighbor siblings such as saved_tracks_by_artist or top_artist_leaderboard, so it misses the top score.

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 implies when to use the tool: when you want an artist-representation ranking across your saved tracks. However, it does not explicitly state when to prefer this over alternatives, nor does it mention any exclusions or competing tools like saved_tracks_by_artist or top_artist_leaderboard.

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