Run Cypher

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

The description states support for write queries (CREATE, SET, DELETE, MERGE, REMOVE), which contradicts the annotation readOnlyHint=true. This is a serious inconsistency. Additionally, no details about permissions, side effects, or error handling are provided.

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 brief (two sentences) and front-loaded with the key purpose and supported queries. It could be slightly more structured but is efficient overall.

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?

The tool has moderate complexity with a write operation and an output schema (though not shown). The description explains the return format but fails to address parameter details and the contradiction with annotations, leaving gaps for an agent to correctly invoke the 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 coverage is 0%, so description must fully explain parameters. It only mentions 'on a specific graph database' for graph_name and lists allowed query types for cypher_query, lacking details on valid graph names, query syntax, or constraints.

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 executes an openCypher query on a specific graph database, listing supported query types (MATCH for read, CREATE/SET/DELETE/MERGE/REMOVE for write) and the return format (columns and rows). This distinguishes it from SQL-based siblings like run_select.

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 specifies the supported Cypher commands for read and write queries, giving clear usage context. However, it does not explicitly exclude alternatives or mention when to prefer a different tool (e.g., SQL queries).

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