nexo_kg_neighbors

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

No annotations are provided, so the description must convey behavioral traits. It only says 'Get direct neighbors' with no details on what 'direct' means, limits, error behavior, or performance implications. This is insufficient for an agent to understand side effects or constraints.

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 sentence, making it concise but lacking essential details. It is not overly verbose, but the trade-off is under-specification. A score of 3 reflects adequate brevity with significant content gaps.

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 there is no output schema and no annotations, the description is too minimal to provide a complete picture. It does not explain what the output looks like, how to paginate results, or any constraints on node types. The tool's complexity warrants more context.

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?

Input schema has 3 parameters with 0% coverage in descriptions. The description adds no explanation of what node_type, node_ref, or relation mean, what formats they accept, or possible values (e.g., are relations like 'child' or 'connected'?). The tool's description does not compensate for the missing schema documentation.

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?

Description clearly states the tool retrieves direct neighbors of a node. Among siblings like nexo_kg_path, nexo_kg_query, and nexo_kg_stats, this tool's purpose is distinct and specific.

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 on when to use this tool vs alternatives like nexo_kg_path for paths or nexo_kg_query for arbitrary queries. The description does not mention when neighbors are appropriate.

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