export_scene

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

The description fails to disclose any behavioral traits beyond the basic action. No details about side effects (e.g., file creation, overwriting), required permissions, or lifecycle implications. With no annotations to compensate, the agent is left uninformed about the tool's runtime behavior.

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 extremely concise with two sentences, front-loading the primary purpose. However, the second sentence about the Ruby tool name is of limited value and could be omitted or integrated elsewhere, slightly reducing its efficiency.

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 description is incomplete for a tool with no annotations and a non-trivial output schema. It does not clarify what 'export the current scene' entails (e.g., file output, format details, or return value), leaving significant gaps for the agent to infer.

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?

The input schema has zero description coverage, and the description does not elaborate on the single parameter 'format'. The lack of explanation for the allowed enum values (skp, obj, etc.) means an agent cannot correctly select or use this parameter without additional 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 action ('Export') and the resource ('the current scene'), leaving no ambiguity about the tool's purpose. It directly addresses what the tool does without any extraneous information.

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?

No guidance is provided on when to use this tool versus alternatives. Without any context on when exporting is appropriate or how it differs from other tools, an AI agent cannot decide whether to invoke this tool over others.

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