collab_density_report

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

With no annotations provided, the description carries the full burden of behavioral disclosure. The 'Read-only' tag is a useful safety signal, but it doesn't disclose potential performance implications of scanning many saved tracks, or any side effects beyond being read-only. No description of the output format beyond ranking.

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, concise sentence that immediately conveys the core function. The key information (collaboration density, ranking) is front-loaded, and there is no extraneous text.

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?

With no output schema, the description provides a general sense of what is returned (ranked collaborations) but doesn't mention response format options or that it may operate on a large library. It's minimally complete for a report-like tool, but lacks detail on how results are presented.

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%, with all three parameters (scan_cap, max_results, response_format) having descriptions in the schema. The tool description adds no additional parameter semantics, so baseline 3 applies.

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?

States a specific purpose: measuring collaboration density by counting saved tracks with 2+ artists and ranking top collaborations. The verb 'measure' and resource 'saved tracks' are clear, though it doesn't explicitly differentiate from sibling tools like featuring_density_report or artist_collab_network.

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?

Provides no guidance on when to use this tool versus similar analysis tools. No mention of alternatives, exclusions, or specific contexts where this is preferred over featuring_density_report or artist_collab_network.

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