nexo_kg_query

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

No annotations are present, so the description must disclose behavioral traits. It fails to mention whether the operation is read-only or has side effects, rate limits, or authentication requirements. The brief description offers no insight into tool behavior beyond the basic action.

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 very concise (one sentence), which is efficient but at the cost of essential details. Every word is necessary but insufficient for a complete understanding. It could be slightly expanded without losing 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?

Given the complexity of a knowledge graph traversal tool with four parameters and no output schema, the description is incomplete. It does not specify return format, constraints on depth or relation, or error handling, leaving significant gaps for the AI.

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 has 0% description coverage, yet the description does not explain any of the four parameters. While names like 'node_type' and 'node_ref' are somewhat self-explanatory, 'depth' and 'relation' require clarification on valid values or behavior. The description adds no value beyond parameter names.

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 'Query knowledge graph — traverse from a node' clearly indicates the resource ('knowledge graph') and the action ('traverse from a node'). It distinguishes from sibling tools like 'nexo_kg_neighbors' (likely immediate neighbors) and 'nexo_kg_path' (path between nodes). However, it does not specify what is returned (nodes, edges, or both), slightly reducing clarity.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention any conditions, prerequisites, or exclusions, leaving the AI to infer usage from the name alone.

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