blend-ai

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

No annotations are provided, so the description carries the full burden. It discloses that the tool creates something new (a write operation) and specifies the return format ('Dict with the created collection's name and parent'), which is helpful. However, it lacks details on permissions, error conditions, or whether the operation is idempotent, leaving behavioral gaps for a mutation tool.

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 well-structured with a clear opening sentence followed by labeled sections for Args and Returns. It's front-loaded with the core purpose. However, the 'Args' and 'Returns' sections could be integrated more seamlessly, and some phrasing ('Empty string uses the scene's root collection') is slightly verbose.

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 no annotations and no output schema, the description does a good job covering the tool's purpose, parameters, and return value. It provides enough context for basic use, though it could improve by mentioning potential side effects (e.g., impact on scene hierarchy) or error cases (e.g., duplicate names), which would enhance completeness for a creation tool.

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 must compensate. It adds meaningful context for both parameters: 'name' is described as 'Name for the new collection', and 'parent' is explained with its optional nature, default behavior ('Empty string uses the scene's root collection'), and purpose ('to nest under'). This goes beyond the schema's basic titles, though it doesn't detail format constraints like string length.

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 specific action ('Create a new collection') and resource ('collection'), including the optional nesting capability. It distinguishes from sibling tools like 'delete_collection' by specifying creation rather than deletion, and from 'move_to_collection' by creating new collections rather than moving objects to existing ones.

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 implies usage through the phrase 'optionally nested under a parent collection' and the explanation of the parent parameter, suggesting when to provide a parent vs. using the root. However, it doesn't explicitly state when to use this tool versus alternatives like 'create_scene' or 'create_object', nor does it mention prerequisites or exclusions.

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