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

Beyond the read-only and idempotent annotations, it discloses the owner-listed public-directory scope, pagination, and the provenance and limitations of ai_origin. The warning never to assume 'not stated' means human-made, alongside the explanation of ACRCloud detection and human_made_only, is especially valuable behavioral context with no output schema present.

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 front-loaded with usage guidance and proceeds logically through scope, search behavior, result semantics, and the next tool. It is nevertheless a dense paragraph with six quoted examples and a filter list that partly duplicates the schema, so it is not maximally economical.

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 nine-parameter read tool without an output schema, it covers scope, selection criteria, search strategy, filtering, sorting, pagination, important result metadata, and the appropriate follow-up tool. Together with the fully documented schema and safety annotations, it supplies the context needed for correct invocation.

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 coverage is 100%, and much of the filter, letter, and sort wording repeats that structured documentation. However, the advice to use a plain theme word in q because titles carry the theme adds genuine search strategy, while the human_made_only explanation clarifies how owner declarations and ACRCloud detection interact.

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 clearly identifies the action and resource: browsing and filtering musical works that owners have listed in the PICA public directory. It also distinguishes this tool from directory_lookup_work, which is explicitly reserved for full details, credits, and audio.

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?

It opens with concrete request patterns, explains how to handle theme or subject searches using q, and says to start here before mood or sound searches because those only narrow results. The explicit handoff to directory_lookup_work for full work details provides an additional clear selection rule.

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