Get Neo4j Knowledge Graph

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the agent knows the operation is safe and repeatable. The description adds minimal context beyond these, only noting that nodes are fetched for a RAG system. It does not elaborate on return format, pagination behavior, or the meaning of 'namespaced endpoint', but it does not contradict the 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?

The description is a single, front-loaded sentence that conveys the essential information without unnecessary words. It is efficient and easy to parse, earning full marks for conciseness.

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?

Despite good annotations and full schema coverage, the description leaves some gaps. It does not explain the 'namespaced endpoint' distinction from sibling tools, nor does it describe the output structure, which is important given the absence of an output schema. The openWorldHint suggests unexpected behaviors, but the description does not address this, making the tool slightly under-specified for an agent.

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 description coverage is 100% for the two parameters (limit and rag_id), each with clear descriptions. The tool description adds no additional parameter-level detail beyond what the schema already provides, so the baseline score of 3 applies.

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 the verb 'Fetch' and the resource 'Neo4j knowledge graph nodes for a RAG system', making the tool's function specific and unambiguous. The parenthetical '(namespaced endpoint)' differentiates it from potentially similar tools like lyzr_kg_get_graph, which likely serves a non-namespaced endpoint.

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 implies usage for Neo4j graph retrieval via a namespaced endpoint, but it does not explicitly state when to use this tool versus the sibling lyzr_kg_get_graph or other Neo4j-related tools. There is no direct mention of alternatives or exclusions, leaving the distinction to inference.

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