search_ffmpeg_docs

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

With no annotations, the description must carry the full behavioral burden. It states it searches help listings, implying a read-only operation, but doesn't mention case sensitivity, regex support, or any side effects. This is adequate but minimal; it adds some context beyond a tautology but lacks depth.

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 concise sentence, front-loaded with the core purpose. No wasted words, though it could have included limit details without losing conciseness. Appropriate length for a simple search tool.

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 tool is simple, and an output schema exists to cover return values. However, the description doesn't explain the role of the limit parameter or the nature of the search (e.g., exact match, fuzzy). It's minimally complete but leaves room for ambiguity about how the query is matched.

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 should compensate. It mentions the query string but says nothing about the limit parameter. Without any schema descriptions, the agent has no guidance on the meaning or default behavior of limit, making this a weak compensation.

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 clearly states the tool searches installed FFmpeg help listings for a query string, using a specific verb and resource. It distinguishes from siblings like run_ffmpeg and get_ffmpeg_docs by narrowing to filters/encoders/decoders help listings, though it doesn't explicitly name alternatives.

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?

No guidance is given on when to use this tool versus siblings like get_ffmpeg_docs or run_ffmpeg. The context of searching help listings is implied but no explicit when-to-use or when-not-to-use advice is provided.

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