Import Three.js asset

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 only states 'Stores' without disclosing side effects, whether the asset replaces existing ones, authorization requirements, or the response format. The term 'bounded' is ambiguous and unexplained, leaving significant behavioral gaps.

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 concise sentence with a clear verb and resource, containing no fluff or redundant phrasing. It is appropriately front-loaded but would benefit from a bit more detail, which is covered under other dimensions.

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 tool has 5 required parameters and no annotations, yet the description does not explain the role of versioning (baseRevision), project scoping (projectId), or data encoding. Although an output schema exists, its content is not shown, so the description still needs to convey outcome expectations. The description is too thin for such a parameter-rich mutation 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%, and the description adds no parameter-specific meaning. It does not explain projectId, baseRevision, name, data, or mediaType beyond what the schema already shows. The enum values are partly implied by 'GLB, PNG, or JPEG', but the description fails to clarify how the parameters relate to the operation.

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 uses a specific verb 'Stores' and identifies the resource ('GLB, PNG, or JPEG asset') and context ('for the current project revision'). This clearly distinguishes it from sibling tools like list_projects or apply_scene_changes, which have different purposes.

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 context by scoping to 'current project revision', but it does not explicitly state when to use this tool vs alternatives, nor give exclusions or prerequisites. No sibling alternatives are mentioned, so guidance is only implicit.

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