blender_import_stl

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

Annotations already declare readOnlyHint=false and destructiveHint=false, indicating this is a mutating operation. The description adds the useful disclosure that relative paths are resolved against the MCP server's working directory. However, it does not clarify whether the import appends to the scene or replaces it, nor what happens if the file is missing or invalid, leaving some behavioral ambiguity.

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 two short sentences with no filler. The first states the core action, and the second adds a critical operational detail. Every sentence earns its place and the most important information is front-loaded.

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 simple one-parameter import tool, the description covers the essential purpose and path-handling behavior. An output schema exists, so return value documentation is not the description's burden. Minor gaps remain around error handling and whether the import is additive, but given the low complexity, the description is nearly complete.

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 schema for the single 'path' parameter is bare (0% description coverage), but the description compensates by explaining how relative paths are handled. This adds meaning beyond the schema, yet it does not specify accepted path formats (e.g., absolute vs. relative, file extension requirements) or whether directories are allowed, so the compensation is partial.

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 uses a specific verb ('Import') with the resource ('an STL file') and target ('into the scene'), clearly stating what the tool does. It is distinguishable from siblings like blender_export_stl and scad_import_stl by the phrase 'into the scene' and the Blender tool name, though it does not explicitly compare itself to alternatives.

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 offers no guidance on when to use this tool versus alternatives such as scad_import_stl or blender_export_stl. The only additional context is the path resolution note, which is operational detail rather than usage guidance. There are no stated prerequisites, exclusions, or recommended scenarios.

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