get_chatflow

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

With no annotations, the description carries the burden of disclosing behavior. It mentions that the output includes the full configuration with nodes and edges, providing some return-value transparency. However, it does not state whether the operation is read-only, what happens if the ID is not found, or any permission prerequisites. Adequate but not rich.

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, front-loaded sentence with no redundant phrases. Every word adds meaning: 'specific ... by ID' narrows to a single resource, and 'full configuration with nodes and edges' clarifies the return content. Ideal conciseness.

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?

For a simple one-parameter retrieval tool with no output schema, the description sufficiently explains the input (chatflowId) and the expected output (full configuration with nodes and edges). It is complete enough for an agent to invoke correctly without needing additional context.

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%, so the schema fully describes the chatflowId parameter. The description merely echoes 'by ID' and does not add new meaning to the parameter beyond what the schema already provides. Baseline 3 is appropriate.

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 uses the specific verb 'Get' with a clear resource ('a specific chatflow by ID') and adds scope ('including its full configuration with nodes and edges'). This distinguishes it from sibling list_chatflows, which retrieves a collection, and from create/update/delete operations.

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 implies the appropriate use case: retrieving a single chatflow's full configuration when the ID is known. This contextively contrasts with list_chatflows, but it does not explicitly state when not to use it or name alternatives. Clear context with no exclusions earns a 4.

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