export_graph

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint. Description adds return format details (JSON with format, content, node_count, edge_count) and a performance caveat for max_nodes (Gephi struggles beyond 50k).

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, well-structured: purpose, formats, usage guidance, return info. No unnecessary words. Front-loaded with main action.

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?

No output schema, but description explains return value. Covers both parameters fully. Distinguishes from siblings. Provides read-only confirmation. Complete for tool complexity.

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%. Description adds default for max_nodes (5000) and performance warning. For format, it provides context (GraphML for Gephi/yEd, etc.) beyond the enum 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 it exports dependency graphs in specific formats (GraphML, Cypher, Obsidian) for external tools. It distinguishes from siblings like visualize_graph (interactive HTML) and get_dependency_diagram (Mermaid/DOT).

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 (for crunching graph in external tools) and when not to use (for interactive HTML or Mermaid/DOT, name alternate tools). Also clarifies it's read-only.

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