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

No annotations are provided, so the description carries the full burden, and it does reasonably well: it discloses the ranking weights (title 3x, genre 2x, mood 1x), the result shape (top 5 tracks with Spotify URLs and matched terms), and a 500-character truncation limit on input. It omits any mention of rate limits, auth, or what happens on zero matches, keeping it below 5.

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?

Three compact sentences, with the core purpose front-loaded before the scoring detail. Every sentence carries information, though the scoring internals are arguably more than an agent needs to select the tool.

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?

There is no output schema, but the description compensates by describing the return payload (top 5 tracks, Spotify URLs, matched terms) and the input truncation behavior. The main gap is the absence of guidance relative to semantic_search and sync_search, which matters given the sibling set.

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% and the single parameter already documents keywords, examples, and the 500-character cap. The description adds no syntax or format detail beyond that, so 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 verb and resource ('Search the CWI placement catalog by keywords') and adds the scoring model, which tells the agent what kind of search this is. It does not explicitly distinguish itself from the overlapping siblings semantic_search and sync_search, so it stops short of a 5.

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?

Usage is only implied: keyword-style matching is suggested by 'by keywords' and the weighted-match explanation, which hints this is lexical rather than semantic. With siblings named semantic_search and sync_search, the definition should say when to pick this one over those, and it does not.

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