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

Describes return contents and the fallback explanation of required edits, but does not discuss side effects or state changes. Annotations indicate readOnlyHint=false, so more transparency about potential non-read-only behavior would be helpful.

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?

Starts with a clear one-line purpose and keeps details relevant. Slightly verbose with repeated references to exact-length edits and for_your_video, but not excessively long.

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?

Compensates for the missing output schema by listing result contents (up to three cues, composer, publisher, watermarked preview) and edit explanation. However, product parameter remains unexplained and no output format is given.

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?

Most parameters have descriptions, but 'product' is completely undocumented. Description adds musical/contextual meaning to duration, cuts_per_min, and has_narration, yet the missing product field leaves ambiguity.

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?

Clearly states a specific action (find music for a video) and resource (AINSOF catalogue), and differentiates from sibling search_music by focusing on video length and duration-based matching.

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 explicit trigger condition: use when a soundtrack is requested for a video and exact duration is available. It does not name alternative tools or exclusions, but the condition is clear enough.

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