get_dependency_diagram

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

Annotations already declare readOnly, destructive, idempotent hints. The description adds that it is read-only and trims to max_nodes most important nodes, which is behavioral context beyond what annotations provide. No contradictions.

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?

Three sentences, no wasted words. First sentence states purpose and outputs. Second sentence clarifies input and trimming. Third sentence clarifies read-only, sibling alternative, and return type. Front-loaded and 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?

Despite no output schema, the description explicitly states the return object structure (format, diagram, nodes, edges). It covers scope interpretation, trimming, and output format. For a 4-parameter tool with no output schema, this is comprehensive.

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%, baseline 3. The description adds semantic context for the 'scope' parameter by specifying input format ('src/tools/') and clarifies that max_nodes limits the diagram size. This adds value beyond the schema descriptions.

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 the tool renders dependency diagrams for file/directory paths as Mermaid or DOT. It specifies the input format ('src/tools/' and 'not a question') and distinguishes from the sibling 'visualize_graph' for interactive HTML visualization.

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 states when to use (file/directory path) and when not to ('not a question'). Provides an alternative tool for interactive visualization, and mentions the trimming behavior based on max_nodes parameter.

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