engine_image_load

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

With no annotations, the description carries full responsibility for behavioral disclosure. It reveals that the tool always saves locally under mcp/melbis/, that png/jpeg/gif/webp are returned inline while svg is text, and that it never reads the local copy—always fetching from the server and overwriting. This is exceptionally transparent about side effects and return behavior.

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?

Three sentences, each dense with essential information, front-loaded with the core purpose and sibling distinction. No redundant phrases or fluff—every word earns its place. This is an exemplary concise definition.

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 fully covers what an agent needs to know to call this tool correctly: the resource type, path structure, local storage behavior, format-specific return behavior, and server-side fetching semantics. Given the lack of output schema and annotations, this is remarkably 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?

Schema coverage is only 50% (file has a description, path does not). The description compensates by explaining the path structure ('By its tree path (templates/<t>/images/...)') and clarifying the 'file' parameter's role ('Local target instead of the mirror path') and the local storage location. This adds substantial meaning beyond the sparse schema.

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 verb 'Load' and the specific resource 'a file of the images tree', and immediately distinguishes it from product files ('NOT a file of a product (those live in engine_files_*)'). This makes the tool's purpose unmistakable and differentiates it from siblings like engine_files_load.

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 explicitly states when NOT to use this tool (for product files) and names the alternative namespace (engine_files_*). It also gives the expected path format (templates/<t>/images/...), which tells the agent exactly how to structure the path parameter. This is strong usage guidance.

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