load_img_to_3d_model

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

With no annotations, the description carries the full burden. It discloses that the server runs until unloaded and frees VRAM upon unload. This is sufficient behavioral context for a simple server start, though it omits potential startup time or dependency checks.

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 extremely concise: two short sentences plus a parameter line, with no fluff. The purpose is front-loaded, and every sentence adds value.

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's simplicity (starting a server), the description covers the lifecycle and memory impact. It lacks output schema details but that is acceptable. It is complete enough for the agent to understand the tool's role and usage.

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 compensates by detailing the single parameter model_dir: 'Path to TripoSR weights directory (uses IMG_TO_3D_MODEL_DIR env var if omitted)'. This adds meaningful guidance beyond the schema's type and default.

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 'Start the local image-to-3D inference server (TripoSR).' This specifies the action (start) and the resource (inference server), distinguishing it from siblings like generate_3d_from_image which perform the actual generation.

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 advises 'load only when you need it' and explains that the server persists until explicitly unloaded. This provides clear usage context, though it does not explicitly contrast with other tools like generate_3d_from_image or unload_img_to_3d_model.

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