Get Flowise Flow Details

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only nature is clear. The description adds context about retrieving nodes, edges, and settings, which goes beyond annotations without contradiction.

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 well-structured with Args/Returns sections and front-loaded purpose. It is not overly verbose but could be slightly more concise by removing redundant self-explanatory sections.

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 simplicity, presence of annotations, and an output schema, the description covers purpose, parameters, and example adequately. No missing critical information.

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?

Despite 0% schema description coverage from context signals, the tool's description explicitly mentions the params object with flow_id and response_format, explains response_format options, and gives a usage example, compensating for the gap.

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 verb 'Get' and resource 'detailed information about a specific chatflow or agentflow', including full configuration. It distinguishes from sibling tools like flowise_list_flows (list) and flowise_analyze_flow (analyze).

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 an example ('Use with the flow ID from flowise_list_flows') implying a prerequisite, but lacks explicit when-to-use or when-not-to-use guidance compared to alternatives like flowise_update_flow or flowise_analyze_flow.

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