search_tracks

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 only states the search action but does not mention whether the operation is read-only, any side effects, or pagination behavior beyond what the schema already provides. This is insufficient for a search tool.

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 a single efficient sentence of 10 words, achieving maximal conciseness. However, it could be slightly more structured by front-loading the key action and including a brief note on pagination without adding clutter. Still, 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?

Given the tool has 4 parameters, no output schema, and no annotations, the description is incomplete. It fails to mention pagination behavior, default values, or the return format (e.g., a list of matching tracks). This lack of context could hamper correct usage, especially for an agent.

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 baseline is 3. The description adds value by linking 'by name' to the track parameter and 'narrowed by artist' to the artist parameter. However, it does not explain the page and limit parameters beyond the schema, so it does not exceed the baseline.

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 the specific verb 'Search' with resource 'tracks' and clarifies the optional narrowing by artist. It clearly distinguishes from sibling tools like search_albums and search_artists by specifying 'tracks', making the tool's purpose unambiguous.

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 description does not provide any usage context, such as when to use this tool versus alternatives like get_track or get_artist_top_tracks. No explicit when/when-not guidance is given, leaving the agent to infer the appropriate scenario from the brief statement.

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