get_plugin_dependency_graph

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

No annotations provided, so description carries full burden. It mentions 'Recursively analyzes dependencies down to leaf nodes', which is a key behavioral trait. Additionally, specifies return format with nodes and edges. Could mention read-only nature, but sufficient.

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?

Description is clear and front-loaded with the primary action. Includes Args and Returns sections. Slightly verbose but no wasted sentences.

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 one parameter and an output schema (not shown), the description covers the essential aspects: input, recursion behavior, and output format. Could mention error cases or limitations, but sufficient for basic use.

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 0%, but the description adds meaning for the only parameter 'short_name' by explaining it is 'The short name of the plugin to analyze'. This provides context beyond the schema's type constraint.

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 'Get dependency graph for a specific plugin in Graphviz format', distinguishing it from sibling tools like get_plugin or get_all_plugins. The verb 'Get' and resource 'dependency graph' are specific and unambiguous.

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?

Implies usage for analyzing plugin dependencies but does not explicitly state when to use it, when not to, or mention alternatives. No guidance on prerequisites or context.

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