get_ffmpeg_docs

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

With no annotations provided, the description must carry behavioral disclosure, and it only contributes 'matches live build', which is a useful but minimal hint that docs are retrieved from the current binary. It does not disclose behavior for unknown names, whether the call hits the network, or any side effects.

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?

The description is a single, front-loaded sentence with no wasted wording, and the core purpose is immediately visible. It is slightly under-specified, but structure and conciseness themselves are good.

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?

Despite the output schema filling in return-value details, the description leaves the 'kind' parameter unexplained and gives no decision aid for siblings. For a tool with no annotations and incomplete param documentation, this is not enough context for correct invocation.

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 0%, so the description must document parameters itself, but it only clarifies 'name'; it never mentions the 'kind' parameter, its default of 'auto', or what values it accepts. A caller cannot determine how to set 'kind' from this description or the schema.

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 opens with a clear verb and resource ('Get detailed help for a filter, encoder, decoder, muxer, or demuxer') and adds a defining constraint ('by name (matches live build)'). It makes the object of the tool obvious, though it never explicitly contrasts itself with the sibling search_ffmpeg_docs.

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?

There is no guidance about when to choose this tool over search_ffmpeg_docs or the other sibling tools. The 'by name' phrase weakly implies a direct-name lookup, but the description does not state that users with an incomplete name should use a search tool instead.

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