render_image

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

Annotations indicate destructiveHint=true, and the description confirms file writing behavior. It adds the crucial detail about absolute path rejection with an environment variable, which is not in annotations. However, it does not mention whether existing files are overwritten or other side effects.

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 concise (two paragraphs) and front-loaded with the core purpose. However, the second paragraph could be more succinct, and some information about parameters could be structured for easier scanning.

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 tool has 10 parameters, no output schema, and destructive behavior, the description is incomplete. It explains output path restrictions but omits return value details, behavior of parameters like frame or trajectory, and potential overwrite warnings.

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?

With 0% schema description coverage, the description only vaguely mentions that representation and coloring are VMD methods, but does not explain the majority of parameters (frame, width, height, output, selection, background, trajectory, etc.). This leaves the agent with minimal guidance on parameter usage.

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 it ray-traces a molecular image headlessly using VMD's Tachyon and saves as PNG. It specifies the verb (render), resource (molecular image), and context (headless, no display). This distinguishes it from sibling tools like render_preset.

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 usage constraints (absolute output paths rejected unless VMD_MCP_ALLOW_ABSOLUTE_OUTPUTS=1) and mentions headless operation, but does not explicitly state when to use this tool versus alternatives like render_preset or list any exclusions.

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