Refresh metadata and preview availability for one Instagram audio asset. Requires Facebook Login. Instagram Login channels return ChannelRefreshRequired.

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

With readOnlyHint/idempotentHint/destructiveHint already set, the description still adds real context: the Facebook Login auth requirement, the ChannelRefreshRequired failure mode for Instagram Login channels, single-request no-auto-pagination behavior, and that provider errors are failures even with HTTP 200. The 'refresh' wording sits in mild tension with readOnlyHint but is consistent with fetching fresh metadata.

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?

Short and front-loaded, but the opening sentence is a verbatim duplicate of the title (including the stray double period), so that portion earns little. The genuinely useful content — pagination, error semantics, login requirement — is compressed but somewhat scattered into fragments.

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 read-only, no-output-schema tool with 6 params, the description covers the key agent needs: auth path, failure mode, single-request semantics, error handling, and field-bounding. It stops short of describing the returned payload, but annotations and the fields parameter mitigate that.

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 only adds the generic 'Use upstream fields to bound data', which does not extend beyond the schema's own field-path guidance, so 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?

The description gives a specific verb+resource — refreshing metadata and preview availability for ONE Instagram audio asset — and identifies the underlying operation (Buffer GraphQL instagramAudio). It is clear what the tool does, though it never explicitly distinguishes itself from siblings get_search_instagram_audio or get_trending_instagram_audio, which an agent must infer.

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 offers procedural guidance ('Use upstream fields to bound data', 'One request, no automatic pagination') but gives no explicit when-to-use/when-not or alternative routing versus the search/trending audio siblings. The login caveat (Instagram Login channels return ChannelRefreshRequired) is behavioral rather than a usage rule.

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