blender_download

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

Description notes 'requires url' and 'optionally import into scene', adding some behavioral context. But annotations are all false and provide no safety hints, so the description carries the burden; it doesn't disclose potential side effects of importing into the scene or what happens on failure.

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?

Two paragraphs with a structured operation list. The term 'portmanteau' is distracting and unexplained, but the overall text is compact and includes only the essentials.

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 covers the two operations and their key requirements. With an output schema present and fully documented parameters, it is complete enough to guide usage; it lacks explicit failure behavior, but that is likely handled by the output schema.

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 descriptions cover all parameters (100%), providing a solid baseline. The description clarifies that 'operation' switches between download and info and that 'url' is expected for download, but adds no new syntax or format details beyond the 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?

Clearly states it downloads from URL and optionally imports, or provides file format info. Distinguishes from sibling import tools by emphasizing the URL source and offering a distinct info operation.

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 operation list clearly indicates when to use download vs info, and the 'requires url' note implies the precondition for download. However, it does not explicitly exclude alternatives like blender_import for local files, so there's clear context but no direct when-not guidance.

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