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

No annotations are provided, so the description carries the full behavioral burden. It usefully enumerates the returned fields (title, artist, Spotify URL, genres, moods), but says nothing about read-only safety, auth requirements, or what happens on an ambiguous partial-title match — a real risk given the schema explicitly allows partial titles. It adds value without closing the gaps.

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 short sentences, zero filler: the lookup semantics come first and the return fields second. Every clause earns its place.

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 one-parameter lookup with no output schema, the description supplies the essential missing piece — the shape of the return. The remaining gap is ambiguity handling for partial titles, which matters here because partial matching is explicitly permitted.

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% for the single parameter, and the property description already documents exact-or-partial titles plus Spotify ID/URL formats. The description merely echoes that, so the baseline 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 ('Look up one catalog track') plus the two accepted identifier forms, so the agent immediately knows this is a single-entity lookup. It implicitly contrasts with the multi-result siblings (search_catalog, semantic_search) via 'one ... track', but never names an alternative, 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: 'by title or Spotify ID/URL' signals the input shape, which suggests this is the tool for a known title or ID. There is no explicit statement of when to prefer it over search_catalog, semantic_search, or sync_search, and no exclusions or prerequisites.

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