blast_radius

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

Core behavior (transitive dependencies) is disclosed, but without annotations, more detail is needed—such as output format (list? tree?), potential performance cost, or whether it includes the node itself. Description is 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?

Single sentence is concise and front-loaded. However, it could be slightly expanded to include output or usage hints without becoming verbose.

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?

No output schema and description does not specify what the tool returns (e.g., list of node IDs, tree, etc.). For a complex graph query tool, this is insufficient for an AI agent to correctly use the results.

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%, and tool description adds no additional meaning beyond the schema. Baseline 3 is appropriate as the description does not enhance parameter understanding.

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 all transitive dependencies of a node, indicating the impact if it changes. Distinguishes from sibling tools like find_references (direct references) and who_calls/who_renders (specific dependency types).

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?

Usage is implied (use when needing to assess impact of changing a node), but no explicit when-to-use, when-not-to-use, or alternatives are provided. Sibling tool names give context but description does not guide selection.

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