arango_add_vertex

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

With no annotations provided, the description carries the burden of disclosing behavioral traits. It only states it is an alias, implying identical behavior to arango_insert, but does not elaborate on side effects, permissions, or any other operational details.

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 extremely short (one sentence) but fails to provide sufficient information. Conciseness is not an excuse for underspecification; it should be more informative.

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 tool has 3 parameters, a required nested object, and no output schema, the description is woefully incomplete. It does not explain the structure of the document, required fields, or what the tool returns, leaving the agent with insufficient context.

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?

The description adds no meaning beyond the input schema. The schema has 3 parameters with low description coverage (33% only for 'database'), and the description fails to explain the semantics of 'collection' or 'document', which are required and involve a nested object.

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 it is an alias for arango_insert and specifies the action 'insert a vertex document into a collection.' This verb-resource combination is specific and distinguishes it from sibling tools like arango_add_edge.

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?

The description only notes it is an alias for arango_insert, but does not provide any guidance on when to use this tool versus other related tools or alternatives. No contextual or conditional usage information is given.

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