query_evidence_graph

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

Discloses read-only nature and output format (JSON arrays aligned with columns). Without annotations, description carries full burden; it provides key behavioral details but could mention potential performance impact or default limit behavior more explicitly.

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?

Two concise sentences, front-loaded with purpose. Every word provides value, no fluff.

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?

All necessary information for a simple two-parameter read-only tool is present, including prerequisites, output format, and limitations. No output schema needed as description covers return behavior.

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 100%, so baseline is 3. Description adds value by contextualizing the query parameter as a constrained Cypher variant and clarifying output structure, which aids parameter understanding beyond schema descriptions.

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 'Execute a read-only graph query using a constrained subset of Cypher', specifying verb, resource, and constraints. Differentiates from sibling 'get_evidence_schema' by recommending it as a preliminary step.

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?

Explicitly instructs to call get_evidence_schema first and warns that the DSL is not full Cypher, providing clear guidance on when and how to use this tool.

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