asset_pipeline

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

Annotations indicate readOnly=false (mutating) and openWorld=true, but the description adds meaningful context: external AI services, environment variable prerequisites, and the presence of check_generation_status implying asynchronous polling. No contradictions with annotations.

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 mostly efficient, with a clear overview and action list. The initial fragment 'External AI asset generation pipeline.' is slightly unnecessary but not harmful. The action list is dense yet well-structured.

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 complexity (multiple actions, external API dependencies), the description covers purpose, prerequisites, and action taxonomy, including polling via check_generation_status. It lacks details on return formats or error handling, but no output schema exists and the description is adequate for tool selection.

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 100%, so each parameter is already well-documented. The description adds an action-level overview but does not provide extra parameter-specific semantics beyond what the schema already includes.

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 is an external AI asset generation pipeline for 3D models and textures using Meshy and Tripo, and lists specific actions. This distinguishes it from sibling tools like manage_asset and manage_texture, which are likely local asset management tools.

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?

Provides clear context: it is an external pipeline requiring API keys, and the action list implies when to use each sub-operation. However, it does not explicitly contrast with sibling tools like manage_asset or manage_texture, so it lacks a clear 'when not to use' statement.

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