reflux_decode

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

No annotations are provided, so the description carries full burden for behavioral disclosure. The description mentions a multi-step process (decode, OCR) but does not disclose potential failure modes, required audio format details, data size limits, or whether the operation is read-only or destructive. The phrasing 'Gives small LLMs eyes' is promotional, not informative about behavior.

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 extremely concise: two sentences with no wasted words. The first sentence explains the transformation pipeline, the second adds a benefit. Every sentence earns its place.

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 complex multi-step tool with no output schema and no annotations, the description is insufficient. It does not explain the output format (text, metadata), error conditions (invalid audio, unsupported modes), or performance considerations. With only one parameter, the description could have provided more context about expected input characteristics (e.g., audio length, quality).

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?

The input schema covers 100% of parameters (only one: audio_base64) with a clear description: 'Base64 encoded SSTV WAV audio'. The description adds minimal extra meaning ('SSTV Audio' context) but mostly repeats what the schema already states. Baseline 3 is appropriate given high schema coverage.

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's function: 'Complete REFLUX decode: SSTV Audio → Image → OCR → Text.' It specifies the input (SSTV audio) and output (text), and uses a unique verb ('decode') and resource ('REFLUX' for SSTV-to-text pipeline). It distinguishes from sibling tools like sstv_encode_text (which encodes text to SSTV) and morse_decode (Morse code).

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?

The description implies use for converting SSTV audio to text, but it does not explicitly state when to use this tool versus alternatives. It mentions giving 'small LLMs eyes', which suggests a use case, but no exclusion criteria or alternatives are named. With siblings like sstv_detect and sstv_encode_ponskaart, more guidance would help.

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