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

Beyond the annotations, the description discloses that no render happens and no charge is incurred, that large files can take minutes, that a retry resumes rather than restarts the download (corroborating idempotentHint=true), and that it creates a scene in the account (matching readOnlyHint=false). Failure handling is spelled out, which the annotations cannot express.

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?

Tight, front-loaded, and every sentence carries operational information: formats, side effects, follow-up calls, polling, failure recovery. The only blemish is an unexplained token ('JANCTION') that slightly interrupts the opening sentence.

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?

Covers a long-running async import end to end: accepted inputs, output (scene_id, though an output schema also exists), cost and render side effects, retry semantics, and error recovery. Nothing an agent needs to invoke or re-invoke this tool correctly is missing.

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 reported as 0%, so the description must carry the load: it enumerates the supported file types (.blend, glTF/GLB, FBX, USD, OBJ, STL, bpy .py), which is the key semantic constraint an agent needs. It also implies the same file object is reused on retry, though it does not explain the file_id/download_url fields.

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?

States a specific verb and resource (import an attached file into a scene of this account), enumerates the accepted formats, and names the return value (scene_id). It also distinguishes itself from sibling tools by naming scene_info and render_preview as the follow-up steps rather than alternatives for the same job.

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?

Gives an explicit sequence of use (import → scene_info → render_preview), a polling instruction for the 'importing' status (call again with the same file after ~30s), and a fallback when fetching fails (ask the user to re-attach or use /upload). There is no ambiguity about when this tool should be called or what to do next.

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