exportScene

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 discloses that the tool exports data (a read-like operation) and mentions the output format (JSON string) and its use case (storage/re-loading), but does not cover potential side effects, permissions needed, or error conditions. This is adequate but lacks depth for a tool with no annotation support.

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, well-structured sentence that efficiently conveys the action, output format, and purpose without any wasted words. It is front-loaded with the core functionality ('Export the current scene as a JSON string') and adds context succinctly.

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 has no parameters, no annotations, and no output schema, the description provides basic completeness by explaining what the tool does and the output format. However, it lacks details on behavioral aspects like error handling or performance, which could be relevant for an export operation. It is minimally viable but has gaps in context.

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 tool has 0 parameters, and the schema description coverage is 100% (empty schema). The description does not need to add parameter information, so it appropriately focuses on the tool's purpose and output. A baseline of 4 is given as it compensates for the lack of parameters by being clear about functionality.

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 specific action ('Export') and resource ('the current scene'), and distinguishes it from siblings like 'exportStandaloneScene' by specifying the output format ('as a JSON string') and purpose ('can be stored and re-loaded later'). It avoids tautology by not just restating the tool name.

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 mentioning 'the current scene' and the purpose of storing/re-loading, which helps differentiate it from tools like 'saveScene' or 'loadScene'. However, it does not explicitly state when to use this tool versus alternatives like 'exportStandaloneScene', leaving some ambiguity.

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