export_graph

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

With no annotations, the description fully discloses behavioral traits: clipboard replacement during export, unused parameters (width/height/dpi have no effect), and file path handling (Windows/WSL paths, missing directory creation). This exceeds the minimum required.

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 efficient, with a clear opening sentence and structured Args list. While not overly long, it could be slightly more concise by omitting the unused parameter defaults, but each sentence adds value.

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's complexity (6 parameters, 2 required, no schema coverage) and the presence of an output schema (though not shown), the description covers all essential aspects: purpose, parameters, behavioral notes, and return value. It is fully adequate for correct invocation.

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?

Schema coverage is 0%, so the description must explain all parameters. It details graph_name, file_path (with path style examples), format (allowed values), and explicitly marks width, height, dpi as unused but retained for API compatibility. This fully compensates for the lack of schema descriptions.

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 'Export a graph to an image file,' specifying the verb (export) and resource (graph to image). This distinguishes it from sibling tools like export_all_graphs, export_graph_sized, and export_worksheet.

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 mentions the clipboard side effect but does not explicitly state when to use this tool versus alternatives (e.g., export_graph_sized for size control). No when-to-use or when-not-to-use guidance is given.

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