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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing further: no note on pagination behavior given limit/offset, no statement of what the mixed catalog result sections contain, and no explanation of the unusual combination of profile search with audiobook/author/album flags.

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?

It is short, but shortness from omission is not conciseness. A single fragment that merely echoes the title leaves every informational need unmet, so it fails the "every sentence should earn its place" test by having no content to earn.

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?

An output schema and full parameter descriptions exist, which lightens the load, but for an 11-parameter search tool sitting beside spotify_search and spotify_profile the description supplies no disambiguation, no scope boundary, and no explanation of the catalog-vs-profile mismatch. An agent cannot confidently pick or scope this tool.

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 all 11 parameters carry their own descriptions (clamps, defaults, prefix behavior, inclusion flags), so the baseline of 3 applies. The description adds no meaning beyond the schema — it does not explain why a "profile search" exposes audiobook, author, and album pre-release flags.

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?

"Spotify profile search" restates the tool name in a noun-fragment form without stating a verb, what a "profile" covers, or how it differs from siblings like spotify_search, spotify_profile, or spotify_artists_search. The agent learns nothing about the resource beyond what the name already encodes.

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?

No when-to-use guidance, no alternatives named, no exclusions. With ~25 other spotify_* tools in the sibling list (including spotify_search and spotify_profile), the agent receives zero routing signal for choosing this one.

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