Fflsharebase64

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

No annotations, so the description must carry the load — and it does disclose what a caller otherwise could not guess: environment-dependent network behavior, forced relay semantics, that qrInTerminal adds ASCII art to the result, and an imperative about link presentation. It stops short of describing session lifetime or the local-server serving model, but the output schema covers the return shape.

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?

Front-loaded with the core action in one sentence, followed by a clearly labeled policy block and a single imperative note. Despite the length forced by 23 parameters, no sentence is redundant and the operational payload is easy to locate.

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 23-parameter tool with an output schema, the description supplies the highest-value missing context: the sandbox networking policy that would otherwise cause silent failures, and the link-presentation requirement. Minor gap is the absence of framing relative to fflShareFile/fflShareFiles and of session lifecycle expectations.

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 coverage is 91%, so the baseline is 3; the description earns above that by explaining the two least self-explanatory parameters (forceRelay, preferredTunnel) with the concrete policy and rationale behind their values. The remaining 22 parameters are adequately covered by the schema alone.

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?

Opens with a specific verb+resource+format: 'Share arbitrary binary data (base64-encoded) using ffl', plus the return contract (sessionId and link). Against siblings fflShareText/fflShareFile/fflShareFiles, the 'base64-encoded binary data' framing makes the distinction clear.

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 an explicit when-to-use rule for a real ambiguity: inside managed sandboxes (ChatGPT Work, Codex sandbox, Claude Code cloud) use forceRelay=True and preferredTunnel='default:web', with an explicit exclusion list for local CLI environments. It does not, however, say when to pick this tool over fflShareFile or fflShareFiles, so selection among siblings is left implicit.

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