search_albums

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

With no annotations, the description must carry the safety/behavior disclosure. 'Search' implies a read-only operation, and the return type is stated, but the description does not mention authentication requirements, rate limits, or error behavior. It is adequate but not rich.

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?

Front-loaded with the core purpose, then usage triggers, args, and returns. The example trigger phrases are a bit redundant with 'Any specific album search request,' but they are useful and the overall length is reasonable.

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?

Covers purpose, when to use, parameter semantics, and return type for a two-parameter search tool. However, with no output schema and no annotations, the 'dictionary containing album search results with detailed information' return description is vague, and the relationship to general search_tidal is not addressed.

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?

The schema has no property descriptions, so the description compensates by explaining query as 'album title, artist name, or combination' and limit as 'Maximum number of albums to return (default: 20)'. Both parameters are given meaningful semantics beyond the raw schema.

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?

Opens with 'Search specifically for albums on TIDAL,' naming a precise verb, resource, and platform. This clearly distinguishes search_albums from sibling tools like search_tracks, search_artists, and search_playlists without needing to open their schemas.

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 explicit trigger phrases ('Find the album [title]', 'Search for albums by [artist]') and a catch-all for any specific album request. It does not explicitly state when to prefer search_tidal or other sibling search tools, but the 'specifically for albums' framing gives clear context.

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