artist_deep_dive

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does disclose the API quota ('1 + one paginated /artists/{id}/albums walk') and that the tool performs a multi-step walk, which is useful. However, it does not explicitly state read-only behavior, error cases, or the shape of the returned dossier beyond the field list.

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 description is two sentences with no filler: the first front-loads what the tool builds and lists its key outputs, and the second adds a tight operational constraint. Every phrase contributes, making it easy to scan.

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?

Given that there is no output schema and no annotations, the description compensates by enumerating the output content and stating the quota behavior. It still omits when-to-use versus sibling deep-dive tools, and it does not describe return formatting, but for the stated complexity it provides enough for an agent to make a reasonable call.

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 already documents all three parameters, including accepted formats for artist_id and the response_format enum. The description adds no parameter-specific meaning beyond what the schema provides, which matches the baseline for high schema coverage.

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 uses a specific verb ('Builds') and a clear resource ('one-artist dossier') with an explicit list of computed fields, so an agent knows what the tool produces. However, it does not explicitly distinguish itself from adjacent sibling tools like artist_discography_timeline, artist_collab_network, or artist_discography_stats, so it misses the top score for sibling differentiation.

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?

There is no guidance about when to choose this tool over alternatives, nor are any exclusions or when-not-to-use conditions stated. The quota note implies a cost consideration, but no explicit usage context or recommended alternative is provided.

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