find_circular_dependencies

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

Discloses algorithm (Tarjan's SCC) and output format (list of cycles, paths, affected packages). Since no annotations, description carries full burden, and it adequately addresses behavioral traits.

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?

Concise with no fluff. Usage examples in USAGE lines are helpful. Could be slightly better structured, but overall efficient.

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 algorithm, output, prerequisite, and parameters. No output schema, but description explains output. Siblings imply analysis context; completeness is good.

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%, so baseline is 3. Description adds usage examples showing packageFilter but no extra semantic detail beyond schema.

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 it detects cycles in packages, with verb and resource. Usage examples reinforce purpose, and the name is self-explanatory. It distinguishes from siblings like get_dependency_graph.

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?

Provides explicit usage examples and a prerequisite ('Requires load_project to be called first'). No explicit when-not-to-use or alternatives, but context is clear.

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