spotify_artist_network

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

No annotations provided, so description carries full burden. It mentions mapping a network but fails to disclose whether it returns a graph, list, or multiple levels; no info on rate limits, data volume, or side effects. Minimal beyond the depth hint.

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?

One sentence, front-loaded with main purpose. Efficient, but could include a bit more context without being verbose. No wasted words.

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?

Despite output schema existence (unknown content), the description leaves out return structure, output format, and how the network is represented. For a network mapping tool with two parameters, it is incomplete.

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 has 0% coverage, so description must compensate. It explains depth parameter's effect at value 2, but does not explain artist_id (implied) or other depth values. Partial explanation; not fully compensating for the lack of schema descriptions.

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 tool maps an artist's network of related artists, using specific verb 'map' and resource 'network'. It hints at the depth parameter by mentioning depth 2 reveals bridge artists, but does not explicitly differentiate from sibling 'spotify_related_artists' which likely returns immediate relatives.

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?

No guidance on when to use this tool vs alternatives like spotify_related_artists or spotify_artist_deep_dive. The only hint is that depth 2 reveals bridge artists, but no explicit when-not or alternative naming.

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