genre_dive_search

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

No annotations are provided so the description must carry the burden, and it does: it discloses the HTTP method and endpoint (one GET /search call), quota cost, and the shape of what is returned (profiles with genre tags) — all beyond the schema. It does not cover empty-result behavior, error conditions, or explicit read-only language, but the GET method implies safety and the disclosed details are meaningful.

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 sentences with no filler: purpose and concrete examples come first, followed by the quota/endpoint note. Every clause earns its place and the most decision-relevant behavioral detail is stated compactly rather than buried in prose.

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 4-parameter tool with full schema coverage, the description adds purpose, output shape, and quota transparency — sufficient for an agent to invoke it correctly. The main omission is explicit differentiation among the many sibling genre/search tools, and with no output schema the return structure is only sketched, though response_format covers the main variants.

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 genre, limit (with its 1–10 cap and default), market (including the from_token behavior), and response_format (with enum meanings) are all already documented in the schema. The description adds only the illustrative genre examples, which is marginal value; the baseline of 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 action — 'Search artists by genre keyword' — with concrete examples (britpop, afrobeat) and the expected output (matching profiles with their genre tags). The genre-keyword angle distinguishes it from name-based search_artists and broader search_advanced tools, so an agent can identify it for genre-oriented discovery.

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 phrase 'the entry point for a genre dive' implies a genre-exploration scenario, which gives some situational context. However, no alternatives are named and no when-not-to-use conditions are given, and with a huge sibling set including search_artists, search_advanced, filter_by_genre, and top_genre_census, the agent receives no explicit routing signal to separate this tool from those.

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