get_neighbors

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

No annotations are provided, so the description carries full burden. It discloses the return structure (entity, type, predicate, direction, fact_id) and explains direction semantics (outgoing/incoming). This is adequate for a read-only query tool, though no rate limits or permissions are mentioned.

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 concise with a brief summary, then separate Args and Returns sections. Every sentence serves a purpose; no redundant or missing information. Ideal structure for a tool with two parameters.

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?

For a simple graph query tool with two parameters, the description is complete. It covers purpose, parameters, and return format in detail. The output schema is effectively documented in the Returns section, so no gaps remain.

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 description adds meaning beyond the input schema by explaining that entity is the name to look up and entity_type is an optional filter for disambiguation. This fully compensates for any low schema coverage and provides clear parameter semantics.

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 it gets immediate neighbors of an entity in the fact graph, explicitly saying 'all entities directly connected by a single fact'. This is specific and differentiates from sibling tools like find_connections or get_entity.

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 provides basic usage info (entity required, entity_type optional for disambiguation) but does not guide when to use this tool vs alternatives like find_connections or query_facts. No explicit when-to-use or when-not-to-use guidance.

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