export_graph

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

Discloses behaviors like optional brotli compression, auto-enabling for small files, streaming for large graphs, and PII redaction. Covers version notes for formats. No annotations provided, so description carries full burden.

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 sentences front-loading key functionality. The second sentence adds version info which may be extraneous but does not detract significantly.

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?

Lacks description of output format or return value (no output schema). Does not mention the filter parameter. For a complex tool with 7 params, more detail on usage is needed.

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 100% with detailed parameter descriptions. The tool description adds high-level context about compression and streaming but does not significantly extend schema semantics.

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 a knowledge graph in various formats, listing specific W3C Linked Data formats. It uses a specific verb ('Export') and resource ('knowledge graph'), and distinguishes from sibling tools like import_graph.

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 (e.g., read_graph). No mention of prerequisites or context where export is appropriate.

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