get_v1_search_music

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

No annotations are provided, and the description does not disclose any behavioral traits (e.g., whether it is read-only, pagination, rate limits, or typical result structure). For a search tool, this is a significant omission.

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?

While short, the description is under-specified and repeats itself. It includes a redundant line break and fails to front-load critical information. Conciseness is not valuable without substance.

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 simple schema but no output schema, the description should at least hint at the response type or search behavior. It is completely inadequate for an agent to use effectively.

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?

The only parameter 'query' has no description in the schema (0% coverage), and the tool description adds no guidance on what constitutes a valid query (e.g., track name, artist, lyrics). The agent cannot infer usage.

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 states 'Search Music' which is vague and does not distinguish this tool from many sibling search tools like get_v1_search_users or get_v1_search_hashtags. The redundancy ('Search Music' followed by 'Search music') adds no clarity.

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 guidance on when to use this tool versus alternatives such as the similar get_v2_search_music or other search endpoints. The description lacks context about the appropriate search scope or query format.

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