Open Kioku Query Evidence Graph

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

Description states read-only nature (matching annotations), explains output format ('JSON arrays aligned with user-selected variables'), and notes the DSL is constrained. Adds useful behavioral context beyond annotations.

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?

Four sentences front-loading the main action, with concise warnings and usage guidance. No wasted words.

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?

Complete for an advanced query tool: explains prerequisites, constraints, output format, and behavioral traits. With output schema present and annotations covering safety, the description fills remaining gaps.

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%, but description adds meaning by linking query parameter to output format and mentioning default limits and caps. Provides slight incremental value over schema.

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?

Clear verb ('Execute'), resource ('graph query'), and constraints ('read-only', 'constrained subset of Cypher'). Distinguishes from siblings by directing to call get_evidence_schema first and to prefer purpose-built tools.

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 inspect get_evidence_schema first, warns that the DSL is not full Cypher, and advises using purpose-built tools when available. Provides clear context for when 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.