youtube_identify_track

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

No annotations are provided, so the description must carry the full behavioral burden. It discloses that the tool identifies from various inputs but does not state whether the operation is read-only, what it returns, whether it performs network calls, or any failure or rate-limit behavior. For a tool with no annotation safety profile, this is a significant gap.

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?

A single sentence with no filler, and the core accepted input formats are front-loaded. It is appropriately concise and every word contributes to the purpose.

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?

The description is not complete enough given there is no output schema and no annotations. It fails to explain return shape, the semantics of limit and regionCode, or what 'identify' yields (metadata, matched track, etc.). An agent can identify the tool but may not invoke optional parameters correctly.

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?

With 0% schema description coverage, the description must compensate for the schema's bare parameter names. It adds useful meaning for the input parameter by listing accepted formats, but it says nothing about limit or regionCode, leaving the agent to guess what those optional parameters control.

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 uses the specific verb 'Identify' and clearly names the resource ('song/video') plus the accepted input forms (YouTube URL, YouTube Music URL, video ID, or search text). It is clear enough to know what the tool does, though it does not explicitly distinguish itself from siblings like youtube_search_videos or youtube_resolve_links.

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?

The description provides no when-to-use guidance, no exclusions, and no mention of alternatives such as youtube_search_videos or spotify_identify_track. The only context is the accepted input forms, leaving the agent to infer when this tool should be selected over siblings.

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