fflShareBase64

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

With no annotations provided, the description carries full burden. It explains that the tool returns a sessionId and link, and that qrInTerminal yields a QR code. However, it lacks details on error handling, security implications, or behavior under failure conditions. The extensive parameter list describes configuration but not overall behavioral traits.

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 lengthy but well-structured. The critical usage note is front-loaded. The Args section is systematic, though slightly verbose. Every sentence adds value, but it could be more concise by grouping related parameters.

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 complexity (22 parameters, no output schema description needed as output schema exists), the description covers all parameters and basic outputs. However, it omits context about the ffl system dependencies, authentication prerequisites, or error scenarios, which would aid completeness.

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 compensate. It provides a detailed Args list for all 22 parameters, explaining each parameter's role (e.g., 'authUser: HTTP Basic Auth username to protect the link'). This fully adds meaning beyond the bare 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 clearly states the tool's purpose: 'Share arbitrary binary data (base64-encoded) using ffl.' It specifies the verb (share), resource (binary data via base64), and output (sessionId and link). This distinguishes it from sibling tools like fflShareFile, fflShareText, etc., which handle file or text sharing.

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 includes an important usage note about presenting the link as clickable, but it does not explicitly state when to use this tool vs alternatives (e.g., fflShareFile for files). Usage context is implied but no exclusions or prerequisites are mentioned.

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