export_to_fanvue

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

No annotations are provided, so the description carries the full behavioral burden. It says the tool publishes, implying a write/external side effect, but does not disclose whether posting is immediate or queued, whether it requires authentication, what happens on failure, or whether the action is reversible.

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 a single front-loaded sentence with no filler. It is efficient, though the brevity leaves important behavioral and usage details unstated rather than merely avoiding verbosity.

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 mutation-style export/publish tool with no annotations and no output schema, the description is thin. It does not explain what success looks like, what is created on Fanvue, or how errors/authentication are handled, leaving the agent with insufficient context to invoke it confidently.

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 100%, so all three parameters are already documented in the input schema. The description adds no additional meaning about imageUrl, caption, or isPaywalled beyond what the schema provides, so the baseline 3 is appropriate.

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 names a specific action pair (export and publish) and a specific destination (Fanvue), which distinguishes it from sibling export tools such as export_to_shopify and export_to_social. It is clear about what the tool does, though it could be sharper about the asset types and whether publishing is immediate.

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?

It does not say when to choose this tool over export_to_social or export_to_shopify, nor does it mention prerequisites such as connected Fanvue accounts, required permissions, or whether the asset must already exist. Usage is only implied by the destination name.

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