Fflhowtosharefromremoteagent

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

With no annotations, the description carries the full burden and does disclose the key behavioral trait: it is a prerequisite step, not the sharing action itself, and it is scoped to a particular class of caller. It does not state side effects, permissions or failure modes, but for a no-parameter guidance tool with an output schema those gaps are small.

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?

Three short sentences with zero waste. The scope restriction is front-loaded ahead of the action, and the exclusion of local agents removes the most likely mis-invocation.

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?

Given zero parameters, an output schema and no annotations, the definition covers the two things an agent needs: who should call it and when in the sequence. It stops short of naming the follow-up tool (fflShareFile vs fflShareFiles vs fflShareText), which would have completed the workflow picture.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline of 4 applies. The description adds no parameter-relevant detail, nor does it need to.

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 states a specific resource (a file or folder on the user's computer) and an ordering role ('call this first'), which distinguishes it from the fflShareFile/fflShareFiles siblings that perform the actual share. It never explicitly says what the tool itself returns (guidance/instructions), so the verb is implied rather than stated.

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?

Explicit when-to-use (cloud-hosted assistants like Grok Bot with no direct access to the user's computer), explicit when-not-to-use (local agents such as Claude Code, Codex, Cursor), and an explicit sequencing rule ('call this first'). This is about as unambiguous as guidance gets.

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