trace_data_flow

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

No annotations, but description discloses traversal of multiple hops, return content (nodes with metadata, edges), and direction semantics. Missing potential behavior like pagination or performance, but adequate.

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 purpose, no wasted words. Every sentence adds value.

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?

Output schema exists, so return values are documented. Description covers essential usage context (direction, not for call graph). Missing edge cases or error conditions, but sufficient for most 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 has 100% coverage. Description adds meaning by explaining direction values and that max_depth has defaults, but largely redundant with schema. Baseline 3 applies.

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?

Clear verb 'follow' and resource 'cross-references from or to an address' with direction options. Distinguishes from sibling tool callgraph by stating not for call graph traversal.

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?

Explicit warning 'Do not use for call graph traversal — use callgraph for that.' Provides alternative and clarifies when to use forward/backward.

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