arango_backup_graph

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

With no annotations, the description should disclose side effects, output details, and constraints. It only states what is included (vertices, edges, metadata) but omits whether the operation is read-only, any required permissions, output format, or the effect of parameters like docLimit and outputDir.

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 sentence with 8 words, no redundancy. Efficiently captures the core action.

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 5 parameters and no output schema, the description provides minimal context. It fails to explain the output (files created), metadata scope, or how documentation limits work. The tool is moderately complex, and the description is insufficient.

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?

All parameters have schema descriptions (100% coverage), so baseline is 3. The description adds no additional meaning about parameters; it does not mention how graph_name, outputDir, includeMetadata, docLimit, or database are used in the export.

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 verb 'Export' and the resource 'complete graph structure including vertices, edges, and metadata.' It differentiates from sibling backup tools like arango_backup (generic) and arango_backup_named_graphs (named graphs) by specifying 'complete graph structure' for a specific 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 such as arango_backup or arango_backup_named_graphs. No context about prerequisites or when not to use it.

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