export_graph

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

No annotations are provided, so the description carries the full burden. It transparently discloses that the file is created in the server data directory, the caller cannot specify a path (path traversal blocked), and the function returns the path. It also notes JSON round-trip compatibility, which is useful behavioral context.

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 concise sentences, front-loaded with the core purpose. The references to [5-E] and [11] are terse but do not detract from clarity; the structure is efficient and scannable.

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 presence of an output schema (which covers return values), the description covers key behavioral aspects: file location, path restriction, and round-trip behavior. It does not explain filter DSL details, but those are in the schema. Overall, it is sufficiently complete for an 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?

Schema description coverage is 100%, so both parameters are well-documented. The description adds minimal extra meaning beyond the schema (e.g., round-trip note for JSON). This meets the baseline for high coverage but does not elevate beyond it.

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 the verb 'export' and resource 'graph to a data format file', clearly distinguishing from import_graph and save_snapshot. The mention of file creation and path return makes the intent unambiguous, though it does not explicitly name sibling alternatives.

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?

Implies usage through the note that JSON round-trips via import, suggesting a use case for export-import cycles. However, it lacks explicit 'when to use vs. not use' guidance or exclusions for other formats or scenarios.

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