vizcom_create_workbench

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

Annotations already declare readOnly=false, destructive=false, idempotent=false, and openWorld=true, so the mutation profile is covered elsewhere. The description adds one useful behavioral fact — the created file is 'isolated' and must target an existing folder — but says nothing about what happens on duplicate names, whether creation is reversible, or what identifier is returned. No contradiction with annotations.

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?

A single front-loaded sentence with no filler, so it is efficient. Its brevity tips slightly into under-specification, but nothing is wasted.

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?

With no output schema, the description should say what an agent gets back (e.g., a workbench/file id to pass to later render tools), and it does not. The folder-existence prerequisite is the one genuinely useful addition; otherwise it is only minimally adequate for a 2-parameter creation tool.

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%, so the description carries the burden for two parameters. It partially compensates for folderId by saying the folder must already exist, but adds nothing about 'name' (length limits 1–120, uniqueness, format) and does not explain the uuid format expectation.

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: 'Create an isolated test file', which tells an agent the operation and the kind of object produced. It does not differentiate from siblings that also create things (vizcom_create_section, vizcom_import_image), and the name/'workbench' vs 'test file' terminology mismatch leaves a small ambiguity about whether this is a file, a canvas, or a workspace.

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 phrase 'in a specified existing folder' implies a prerequisite (the folder must already exist) but does not state when to use this tool versus the other creation tools in the sibling list, nor when not to use it. Usage context is only implied, not spelled out.

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