vynly-mcp

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes the permanent nature of the post ('permanent post') and the requirement to declare AI provenance if missing, which are critical behavioral traits. However, it omits other important details like authentication needs, rate limits, error handling, or what happens on success/failure.

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 appropriately sized and front-loaded, with the core purpose stated first. Both sentences earn their place: the first defines the tool's function and input options, and the second provides crucial behavioral guidance on AI provenance. There is no wasted text or 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?

Given the complexity (9 parameters, no annotations, no output schema), the description is moderately complete. It covers key aspects like the tool's purpose, input methods, and AI provenance handling, but lacks details on output format, error conditions, or prerequisites. For a mutation tool with rich parameters, more contextual information would be beneficial.

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 67% (6 of 9 parameters have descriptions), so the description must compensate. It adds significant value by explaining the purpose of imagePath, imageUrl, and imageBase64 as input options, and clarifies the declaredSource parameter's role in specifying AI tools when provenance is missing. This goes beyond the schema's basic descriptions and enum list.

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 specific action ('Publish an AI-generated image as a permanent post') and resource ('on Vynly'), distinguishing it from sibling tools like vynly_post_spark (likely for text/spark content), vynly_read_feed (reading), and vynly_search (searching). It precisely communicates the tool's function without being vague or tautological.

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 provides clear context for when to use this tool (for posting AI-generated images) and includes implicit guidance on when not to use it (e.g., for non-image content, which might be handled by vynly_post_spark). However, it lacks explicit alternatives or exclusions, such as specifying when to use sibling tools instead.

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