artist_deep_cuts

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

No annotations are provided, so the description carries the behavioral disclosure burden. It does a solid job by revealing the exact matching algorithm, the ranking order, and a concrete quota ('2 walks + one chunked /albums?ids= fan-in'). It does not explicitly state read-only status or failure behavior, but the resource-consumption detail is valuable.

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 tightly written sentences with no filler. The core definition is front-loaded, and the quota sentence earns its place by informing an agent about the cost of invocation.

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?

The description is largely complete for a complex analysis tool: it defines deep cuts, explains ranking, and discloses quota behavior. It does not describe edge cases like an artist with no deep cuts, but the response_format parameter in the schema covers the output contract.

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 75%, with artist_id, max_releases, and response_format already documented in the input schema. The description adds context to max_releases through the 'recent albums and singles' definition, but it does not clarify max_results, which lacks a schema description.

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 states a specific verb ('Finds'), a clear resource ('an artist's deep cuts'), and a precise operational definition: tracks whose normalized title appears on exactly one release across recent albums and singles, ranked longest-first. This makes the tool's purpose unambiguous and distinguishes it from generic siblings like deep_cuts_finder or b_sides_finder.

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 no explicit guidance on when to prefer this tool over alternatives. With many sibling tools such as artist_deep_dive, deep_cuts_finder, and artist_discography_stats, an agent is left to infer which is appropriate based on names alone.

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