dependencies

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

No annotations provided; description does not state that tool is read-only or safe, nor any potential side effects or requirements.

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?

Short, front-loaded description with three sentences plus parameter explanations; no redundant information.

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?

Covers main purpose and two parameters; output schema exists but not shown. Missing repo_path explanation and behavioral transparency, but otherwise adequate for a simple tool.

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?

Explains exclude_dirs and output_format in description, but repo_path is left unexplained despite being a key parameter. Schema coverage is 0%, so description partially compensates.

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?

Clearly states circular imports and layer structure analysis; distinguishes from siblings like architecture or blast_radius by focusing on dependency graph and refactoring use case.

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?

Explicitly says 'Use before refactoring to understand the dependency graph', but does not mention when not to use it or compare to alternatives like architecture or blast_radius.

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