shortest_path

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

No annotations and description lacks behavioral details such as what the output is, how the path is computed, or what happens if no path exists. Only states 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?

Description is a single sentence, very concise. However, it sacrifices necessary detail for brevity. It could be expanded slightly to cover key aspects.

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 zero schema descriptions and no annotations, the description is incomplete. It does not provide enough context for an AI agent to correctly invoke the tool, especially regarding parameter meaning and behavior.

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 0%, and the description does not explain the parameters (source, target, max_hops). No indication that source and target are concept identifiers or what max_hops limits.

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 it finds the shortest path between two concepts in the Gonka documentation graph, with a specific verb and resource domain. It distinguishes from sibling tools like get_neighbors or graph_stats.

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 versus alternatives (e.g., get_neighbors, query_graph). No prerequisites or exclusions are mentioned.

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