Flow Summary

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

With no annotations, the description must fully disclose behavioral traits. However, it only states the output type ('compact semantic summary') without mentioning side effects (likely read-only), auth needs, rate limits, or what 'semantic' means. This is insufficient for an AI to assess safe usage.

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 a single sentence with no waste, but it is somewhat under-specified. It earns high marks for conciseness but loses slightly for lacking structure like bullet points or parameter details.

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 absence of output schema and annotations, the description should provide more context about return format, usage examples, or edge cases. It is too minimal to fully guide an AI agent.

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 single parameter 'flowId' has 0% schema description coverage, and the description does not mention it at all. It fails to explain that omitting it returns a summary of the whole runtime, adding no value beyond the schema.

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 returns a 'compact semantic summary' for a flow or whole runtime, using a specific verb and resource. It distinguishes from sibling tools like 'node-red-graph-export' and 'node-red-graph-dependencies' by focusing on summarization, though 'semantic' could be more precise.

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?

No guidance is provided on when to use this tool versus alternatives like other graph tools. The description does not mention prerequisites, exclusions, or scenarios where this tool is preferred.

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