flowzap_export_graph

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the tool's function as an export operation that outputs a structured JSON graph, implying it is read-only and non-destructive, but does not specify details like error handling, performance characteristics, or whether it requires specific permissions. While it adds useful context about use cases, it lacks comprehensive behavioral traits beyond the basic operation.

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?

The description is front-loaded with the core purpose in the first sentence and efficiently adds use cases in the second, with zero wasted words. Every sentence earns its place by clarifying the tool's function and applications, making it appropriately sized and well-structured for quick understanding.

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 the tool's moderate complexity (exporting structured data), no annotations, and no output schema, the description is adequate but incomplete. It covers the purpose and usage context well, but lacks details on output format specifics, error conditions, or behavioral nuances. For a tool with no structured output documentation, more information on the JSON structure or limitations would enhance completeness.

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?

The input schema has 100% description coverage, with the single parameter 'code' documented as 'FlowZap Code to parse into a graph structure'. The description adds marginal value by reinforcing that the tool parses 'FlowZap Code' into a graph, but does not provide additional semantics beyond what the schema already states, such as format examples or constraints. Baseline 3 is appropriate given the high schema coverage.

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 specific action ('Export FlowZap Code as a structured JSON graph') and resource ('FlowZap Code'), distinguishing it from siblings like 'flowzap_validate' or 'flowzap_diff' by focusing on structural export rather than validation or comparison. It explicitly mentions the output format ('lanes, nodes, edges') and use cases ('inspect diagrams structurally, query relationships, or analyze workflow patterns'), making the purpose highly specific and differentiated.

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?

The description provides clear context on when to use this tool ('to inspect diagrams structurally, query relationships, or analyze workflow patterns without re-parsing DSL'), implying it is for analysis rather than modification. However, it does not explicitly state when not to use it or name alternatives among siblings, such as 'flowzap_artifact_to_diagram' for visualization or 'flowzap_validate' for syntax checking, leaving some ambiguity in tool selection.

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