exportScene

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the return contract ({ success, data?, message?, error? }) which is helpful, but it does not explain what 'current' means across sessions or whether this includes transient UI state, though the output schema may cover return specifics.

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?

Two efficient sentences: the first states the action and target, the second provides the return shape. Every word earns its place—no filler or repetition of the tool name.

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?

For a read-only, zero-required-parameter tool with an output schema and clear annotations, the description is largely sufficient. Minor gap: it doesn't clarify whether 'current' view/layer/entity state includes all sessions or just the one tied to sessionId, but given the simplicity and existing structured data, this is acceptable.

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 description does not discuss parameters, but the input schema covers 100% of the single optional sessionId parameter with its own description. The baseline of 3 applies because the schema handles semantics; no extra value is added by the tool description.

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 the specific verb 'Export' and names the exact resources: 'current view, layer, and entity state' as JSON. It clearly differentiates from siblings like getView (which likely just returns view) or queryEntities (which queries specific entities) by indicating a full export of scene state.

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 gives no explicit guidance on when to use this tool versus alternatives like getView or queryEntities. The usage context (e.g., 'use when you need the complete scene snapshot') is only implied by the word 'Export' and is not spelled out for the agent.

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