vizcom_render_pipeline

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

Adds real context beyond annotations: it discloses that credits are consumed, that exactly one render is submitted (reinforcing non-idempotency), that the input must be a PNG, and what identifiers come back. It stops short of stating what happens on failure or how long a render takes.

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, front-loaded with the action, followed by the follow-up chain and the cost warning. No wasted wording.

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 credit-consuming mutation with an open-world, non-idempotent profile and no output schema, the description covers the workflow and cost but leaves the parameter space essentially undocumented. An agent would still grope on style, influence, and workbenchId.

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% for 5 parameters, so the description must compensate. It only clarifies the file format (PNG) and implies the prompt; it says nothing about style enum choices, influence range, or workbenchId, leaving four parameters unexplained.

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?

States a specific verb and resource: upload a PNG and submit one render, returning drawing and prompt ids. It does not explicitly distinguish itself from the sibling vizcom_render_sketch or vizcom_upload_sketch, so an agent must infer which render entry point applies.

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 routes the agent to vizcom_get_result for polling and vizcom_download_result for retrieval, which is clear follow-up guidance. It gives no when-not guidance or differentiation from vizcom_render_sketch, which is the main gap.

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