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

Adds real context beyond the annotations: results come back ranked, a cursor is returned when more exist, the same tag/facet/scope/cursor must be reused, and page size should not change. It does not reconcile the surprising annotation profile (readOnlyHint=false, idempotentHint=false) for what reads like a pure browse operation, leaving the agent unaware of any side effects such as quota or browse tracking.

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?

Roughly four sentences, each load-bearing: selection criteria first, the sibling redirect second, return/pagination behavior last. No repetition of schema enums or annotation restatement.

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?

With no output schema, the description supplies return shape (ranked results plus cursor) and paging protocol, which is enough to call it correctly. The remaining gap is the undefined scope parameter and the unexplained non-read-only annotation.

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 only 20% (just page_size), so the description carries the burden. It usefully explains tag exactness, facet values, and cursor continuation semantics, but the required 'scope' parameter (music vs sfx) is mentioned only incidentally and never defined, leaving a required enum undocumented in both places.

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 (browse) and resource (AINSOF category/tag) plus the facet dimension (genre, mood, instrument, use), which matches the facet enum exactly. It explicitly distinguishes itself from search_music, so an agent can choose between them without opening a schema.

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?

Gives an explicit when-to-use clause ('only when the user explicitly wants to browse a category or tag') and an explicit when-not clause routing written briefs, refinements, artist or track names to search_music. It also gives continuation instructions for paging.

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