get_transitive_deps

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

Discloses dynamic import filtering, depth limits, and return format (object mapping IDs to depths). Transparent about limitations beyond schema.

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?

Well-organized with headers and bullet points. Every sentence provides value without redundancy. Front-loaded with purpose.

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?

Describes return format despite no output schema. Covers dynamic import filtering. Could mention behavior on files outside project, but overall complete.

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 already documents parameters clearly (100% coverage). Description adds default depth, max recommended, and fuzzy matching detail, adding value.

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 it gets transitive dependencies up to a specified depth, distinguishing it from direct dependency tools like get_dependencies. Uses specific verb-resource combination.

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 lists use cases (understanding full chain, analyzing coupling, planning refactoring) and caveats (static imports only), guiding appropriate usage.

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