retrieve_related_entities

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

No annotations provided, so description carries full burden. It mentions n-hop traversal but omits crucial behavioral details such as output format (list vs. tree), pagination, performance implications, or whether full entity snapshots are returned (though schema hints via include_entities). Lacks depth for a multi-hop relationship tool.

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?

Two sentences, front-loaded with key action. No fluff, though it sacrifices completeness for brevity. Still earns a 4 for efficiency.

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?

With 5 parameters and no output schema or annotations, the description is too sparse. It fails to explain return values, edge cases (e.g., empty results), or how the multi-hop traversal is represented. More details are needed for practical use.

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% with detailed parameter descriptions (e.g., max_hops default 1, direction enum values). Description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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 explicitly states function: retrieve entities connected via relationships, with n-hop support. Clearly distinct from siblings like 'retrieve_entities' (which likely retrieves entities by ID or criteria) and 'retrieve_graph_neighborhood' (which focuses on graph structure).

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 when-to-use or when-not-to-use guidance provided. Does not mention alternatives like 'retrieve_graph_neighborhood' or 'list_relationships', leaving the agent to infer selection context.

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