jambavan_graph_path

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

No annotations are provided, so the description carries the full burden. It discloses the algorithm (BFS) and the behavior of include_inferred, but does not mention side effects, rate limits, auth needs, or what happens if no path exists. Adequate but incomplete.

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 two sentences with no wasted words. It front-loads the core purpose and provides essential guidance concisely.

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?

The description explains the algorithm and prerequisite, but does not describe the return value or format. Without an output schema, the agent is left guessing what the tool returns (e.g., a list of nodes). Partially complete.

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 coverage is 100% with all 4 parameters described in the schema. The description adds little beyond what the schema provides, only restating include_inferred use. 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?

The description clearly states 'Find the shortest path between two graph nodes/symbols', specifying the verb (find) and resource (shortest path). It distinguishes itself from sibling tools like jambavan_graph_query and jambavan_graph_report by focusing on path-finding.

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 explicitly advises to 'Call jambavan_index first' as a prerequisite and explains when to use include_inferred. However, it does not explicitly state when not to use this tool compared to alternatives, leaving some ambiguity.

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