import_image_as_plane

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

With no annotations provided, the description must fully disclose behavioral traits. It only states the high-level action (import as textured plane) but does not mention side effects, whether it modifies existing objects, whether it requires specific file formats, or what happens on failure. It does not describe any state changes or call requirements, leaving significant behavioral ambiguity.

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 appropriately concise with a single sentence that is front-loaded with the core action. However, it is under-specified, missing essential operational details. While it does not waste words, it sacrifices completeness for brevity, making it less useful than a slightly longer but more informative description.

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 simplicity (2 parameters), the description is incomplete. It lacks any information about the location parameter, the filepath requirements, what the tool returns (despite having an output schema), and any preconditions. The absence of guidance on parameter semantics and behavioral expectations leaves the tool under-documented for reliable invocation.

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 gives no information about the parameters 'filepath' or 'location'. The filepath's expected format, supported image types, or default behavior of location are entirely unexplained. The description fails to compensate for the lack of schema details, making it impossible for an agent to correctly populate the parameters without external knowledge.

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 verb 'Import' and the resource 'an image file as a textured plane', which is a specific and understandable purpose. It distinguishes itself from the generic sibling 'import_file' by specifying the result is a textured plane. However, it does not elaborate on what 'textured plane' implies (e.g., does it create a new object, apply a material?), so it is not fully explicit about its exact scope.

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 such as 'import_file' or other import-related tools. There is no mention of prerequisites, restrictions, or situations where this tool is preferred. An agent would have to infer the intended use case from the tool name alone, which is insufficient.

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