blast_radius

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

With no annotations, the description fully discloses behavior: BFS algorithm, inverted call edges, returns specific fields (direct_callers, all_impacted, etc.), and scope (Python files only). No hidden side effects or destructive actions are implied.

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, front-loads the purpose, and includes all essential information without verbosity. Every sentence earns its place.

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 no annotations or output schema, the description covers purpose, algorithm, input parameters, return fields, and file type restriction. It is complete for an agent to understand and use this tool correctly.

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% (both params described), so baseline is 3. The description adds value by explaining the algorithm context (BFS over inverted call edges) and linking the parameters to the analysis process, though the schema already defines them clearly.

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 'Reverse-call-graph impact analysis for a Python function', specifying the verb (analyze impact), resource (Python function), and methodology (BFS over inverted call edges). It distinguishes from sibling tools like index_repo and security_surface which have different purposes.

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 implicitly defines usage: when you need to know which functions are affected by changing a target function in a Python file. It does not explicitly compare with siblings, but the context is clear. The restriction 'Python files only' provides a clear constraint, earning a 4.

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