export_scene

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered structurally. The description's added value is 'No file is written', which usefully disambiguates the 'export' name so the agent knows nothing is persisted server-side, but it says nothing about the payload format or size.

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 short sentences with no filler, and the core fact (what is returned) is front-loaded before the clarifying caveat about no file being written.

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 zero-parameter, read-only tool with no output schema, the description carries the essential information: the return is an embedded .excalidraw document, not a file path. The only gap is that it doesn't say whether the document is raw JSON or encoded, which matters for a client that must save/import it.

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 takes zero parameters, so there is no parameter meaning to convey and the baseline of 4 applies. The description correctly avoids inventing options and makes clear the call is argument-free in effect.

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 ('Return') and resource ('embedded .excalidraw document'), and adds the outcome ('for the client to save/import'), which is concrete enough to picture the result. It does not explicitly distinguish itself from near siblings like get_scene, save, or export_png, so an agent must infer the boundary.

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 phrase 'for the client to save/import' implies the use case (you want the serialized document rather than an in-server action), but there is no explicit when-to-use versus get_scene/save/export_png guidance or any stated precondition. Usage is implied rather than directed.

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