render_model_preview

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

Despite no annotations, the description discloses deprecation, the single-angle limitation, and the wrapper nature. It could mention return format or error behavior, but overall transparent about its capabilities and shortcomings.

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 and front-loaded with the most critical information (deprecated, recommended alternative) followed by a brief Args section. No redundant sentences.

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 adequately covers the tool's purpose, parameters, limitations, and provides clear guidance to avoid it. It does not specify the output format, but given the deprecated status and preference for visualize_model, this is acceptable.

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 fully compensates with an Args section explaining each parameter: file_type examples for file_path, default values for width/height, and a hex color example for color.

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 explicitly states the tool renders a model preview, is deprecated, and distinguishes itself from the preferred alternative 'visualize_model' by noting it renders only 1 angle with fewer features.

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 clearly advises against using this tool, recommending 'visualize_model' instead, and provides specific reasons (multi-angle, auto-framing, colored 3MF, quality scores) for preferring the alternative.

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