vynly_post_spark

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

Discloses all behavioral traits: auto-delete after 24 hours, image-only restriction, requirement for exactly one of three image inputs, reliance on Vynly agent token in VYNLY_TOKEN env var, and return of created spark object with id, url, and expiry timestamp. No annotations present, so description fully handles transparency.

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?

Highly concise and well-structured: first sentence captures purpose and key constraints, followed by usage guidance, parameter clarification, and return value description. Every sentence adds value without redundancy.

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 no output schema, the description specifies return fields (id, url, expiry timestamp) and authentication requirement. With 7 parameters fully described in schema, the description provides sufficient operational context for correct tool invocation.

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 100% with detailed parameter descriptions. The tool description adds high-level context like the mutual exclusivity constraint (exactly one of imagePath/imageUrl/imageBase64) and clarifies that declaredSource is optional but recommended, which goes beyond 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?

Clearly states the tool publishes an AI-generated image as a 24-hour ephemeral 'spark' on Vynly, specifying it is image-only (no caption/tags). It distinguishes from sibling tool vynly_post_image by contrasting ephemeral vs permanent posts.

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?

Explicitly provides when to use: for experiments, work-in-progress, or content that doesn't need permanent timeline. Directly recommends alternative vynly_post_image for permanent posts, offering clear guidance on tool selection.

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