export_diagram

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

With no annotations, the description fully discloses behavioral traits: JSON is saved directly by the server, while PNG/SVG are generated by the browser and sent back. It also notes the prerequisite session and browser connection, and multi-session targeting. This goes beyond a simple 'export' statement.

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: a single opening sentence followed by three bullet-point notes. Every sentence adds value without redundancy. The main action is front-loaded, making it easy for an agent to parse quickly.

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 no annotations or output schema, the description is fairly complete: it covers prerequisites, behavior differences between formats, and multi-session support. It lacks details on expected return values or error handling, but these are minor gaps for a relatively simple export tool.

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 already covers all parameters with descriptions (100% coverage). The description adds minimal value for parameters, only noting that 'sessionId' targets a specific session. The format options are clear from the enum, and path is self-explanatory.

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 tool exports the current diagram to PNG, SVG, or JSON. It uses a specific verb ('Export') and resource ('current diagram'), and the listed formats differentiate it from sibling tools that create, delete, or update diagrams.

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 provides clear usage context: requires 'start_session' to be called first and the browser to be connected. It also explains multi-session support via 'sessionId'. However, it does not explicitly state when not to use this tool or mention alternatives, though no sibling tool directly competes.

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