blender_download

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

Without annotations, the description carries full burden for behavioral disclosure. It mentions the 'download' operation requires a URL and optionally imports, but omits details such as side effects (e.g., file creation), network behavior, error handling, or permission requirements. The tool's mutability and potential impacts are not addressed.

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 brief and well-structured, using a top-level summary and bullet-points for operations. Every sentence adds value, with no extraneous text. It is front-loaded and easy to scan.

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 moderate complexity (two operations, 5 parameters) and the existence of an output schema, the description covers the core functionality. It explains the two operations and provides a hint about each. However, it could elaborate on the 'info' operation's return structure or usage recommendations for different parameters.

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 100%, so the baseline is 3. The description adds that the 'url' parameter is 'required' for download and that 'info' provides supported formats, but these details are largely redundant with the schema. No additional semantic meaning beyond the schema is provided.

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 tool's two main operations: downloading from a URL and optionally importing into the scene, and getting supported format info. It uses specific verbs and resources, distinguishing it from sibling tools like blender_import or blender_export.

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 outlines the two operations ('download' and 'info') and notes that 'download' requires a URL. However, it does not explicitly state when to use this tool versus alternatives like blender_import or blender_mesh, nor does it mention cases where the 'info' operation is preferred.

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