origin_export_graph

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

No annotations provided, so description carries full burden. It discloses behavior for active vs named graph via 'graph_name' parameter and 'overwrite' flag, but lacks details on error handling, file format restrictions, or side effects.

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?

Single 14-word sentence, front-loaded with the action and resource. However, could be expanded slightly to improve completeness without losing conciseness.

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?

Despite having an output schema, the description is too minimal. It fails to specify supported output formats (e.g., PNG, PDF), file extension expectations, or whether the export covers the entire graph or a specific plot. Incomplete for a 3-parameter tool with no annotation support.

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% with no descriptions for parameters. Description only hints at 'graph_name' (active vs named) but does not explain 'path' (output location) or 'overwrite' (overwrite existing file?). Minimal added value beyond the schema itself.

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?

Description clearly states the tool exports a graph to an image/PDF file, with specific verb 'export' and resource 'graph'. It distinguishes from sibling tools like 'origin_get_graph_info' which only retrieves info, but lacks specificity about supported file formats.

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?

No guidance on when to use this tool versus alternatives like the plotting tools or format_graph. No mention of prerequisites or context for choosing between active or named graph.

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