get_visualization_artifact

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

With no annotations, the description carries the full burden. It does disclose the output behavior (MCP image result), but it does not mention related traits such as whether the artifact is consumed, what happens if the ID is invalid, or any prerequisites. This is minimal but non-contradictory.

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 a single, front-loaded sentence with no unnecessary words. Every element contributes to understanding the tool's function and output.

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?

The description is too sparse for a tool in a multi-step workflow. It lacks context about where the artifact comes from (likely from visualize_cfd_results), what to do if the artifact doesn't exist, and how the returned MCP image result should be used. The absence of an output schema and annotations increases the need for descriptive context.

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?

The input schema has one required parameter (artifact_id) with 0% schema description coverage. The description does not elaborate on what artifact_id means, how to obtain it, or any format expectations, completely failing to compensate for the missing schema documentation.

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 tool loads a previously generated visualization artifact and converts it to an MCP image result. This specific verb-resource pairing distinguishes it from sibling tools like visualize_cfd_results, which generate artifacts, while this one retrieves them.

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 'previously generated' implies usage after a generation step, but it does not explicitly mention when to use this tool vs alternatives, nor does it exclude scenarios. There is no explicit guidance or naming of prerequisite tools like visualize_cfd_results.

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