Get instagram audio

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

Goes well beyond the annotations by disclosing authentication requirements (Facebook Login), the ChannelRefreshRequired failure mode, that it is a single request with no automatic pagination, and that provider errors surface as failures even with HTTP 200. Annotations only cover the safe-read/idempotent profile, so this operational detail is genuinely additive.

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?

Dense and front-loaded: the core action leads, followed by auth, error, and pagination constraints. It reads as a compressed run-on, but nearly every clause carries actionable information.

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?

Covers auth, error, and pagination behavior for a 6-parameter tool with nested objects and no output schema. The main remaining gap is return-value shape, which the description leaves entirely to the caller since no output schema exists.

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 100%, so the schema already documents fields, account, audioId, channelId, payload, and payload_file. The description adds only a light hint on bounding data via upstream fields, so the baseline 3 applies.

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+resource+scope: 'Refresh metadata and preview availability for one Instagram audio asset.' The singular 'one ... asset' implicitly separates it from the list-style siblings get_search_instagram_audio and get_trending_instagram_audio, though those siblings are never named.

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 concrete preconditions and exclusions: 'Requires Facebook Login' and 'Instagram Login channels return ChannelRefreshRequired,' which tells the agent when this call will fail. It also scopes work via 'Use upstream fields to bound data,' though it never explicitly routes to the search/trending alternatives.

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