Read Neo4j Cypher

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

The description only restates the read-only nature already captured by annotations (readOnlyHint, idempotentHint, destructiveHint). It adds no extra context about query execution, result formatting, error handling, or any potential side effects.

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?

A single, clear sentence conveys the purpose without wasted words. It is front-loaded with the verb and resource, making it easy to parse.

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 is relatively simple and the annotations cover safety. However, the description is minimal—it doesn't mention what the query returns or that params is optional (though the schema does). Given no output schema and no usage guidance, the description could provide a bit more context about result expectations or common use cases.

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 input schema already provides complete descriptions for both parameters (query and params), so the baseline is 3. The description does not elaborate on parameter usage or add any additional semantic meaning.

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 defines the action ('execute') and resource ('read Cypher query on the Neo4j database'), easily distinguishing it from siblings like write_neo4j_cypher and the specialized search tools. The 'read' qualifier immediately signals its scope.

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 offers no guidance on when to choose this tool over alternatives. It doesn't mention that raw Cypher should be used for arbitrary reads or that search tools are for specific query patterns. There are no explicit exclusions or prerequisites.

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