create_assets

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Create' implies a mutation operation, but the description doesn't state whether this requires specific permissions, what happens on failure (e.g., partial creation), if it's idempotent, or what the response looks like. For a complex creation tool with multiple asset types, this is a significant gap in transparency.

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 a single, efficient sentence: 'Create one or more assets'. It's front-loaded with the core action and resource, with zero wasted words. This is appropriately concise for a tool where detailed parameter semantics are covered in the schema.

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 complexity (multiple asset types with nested schemas), no annotations, and no output schema, the description is incomplete. It doesn't explain the return values, error handling, or behavioral nuances like whether assets are created synchronously/asynchronously. For a creation tool with such rich input structure, more context is needed to guide the agent effectively.

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%, with detailed descriptions for all nested parameters (e.g., 'Array of assets to create' for the main parameter). The description adds no additional parameter information beyond what's in the schema. According to the rules, with high schema coverage (>80%), the baseline is 3 even with no param info in the description.

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 'Create one or more assets' states the verb (create) and resource (assets), making the basic purpose clear. However, it's vague about what types of assets can be created (CSS, folder, HTML, material, script, shader, template, text) and doesn't distinguish from sibling tools like 'instantiate_template_assets' or 'list_assets'. It's adequate but lacks specificity.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, when to choose this over sibling tools like 'instantiate_template_assets' (for templates) or 'add_components' (for components), or any context for asset creation. This leaves the agent without usage direction.

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