arango_graph_traversal

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

No annotations provided and the description lacks any behavioral details such as performance, side effects, limits, or result structure. The agent has no insight into the tool's behavior beyond being an alias.

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 very short but fails to provide substantial information. It is terse rather than concise, offering minimal value beyond stating it is an alias.

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 complexity of graph traversal with 9 parameters, the description is severely inadequate. It does not explain what the tool does, its inputs, outputs, or how it differs from similar tools.

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 only 11%, with only the 'database' parameter having a description. The tool description does not explain any parameters, leaving the agent without guidance on how to fill them.

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?

Clearly states it is an alias for arango_traverse, which identifies the tool's function as graph traversal. However, it does not elaborate on what traversal means in this context.

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 arango_traverse or other traversal tools. The description only notes it is an alias, leaving the agent without context for selection.

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