get_flow

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

With no annotations, the description carries the full burden of behavioral disclosure. It clearly indicates a read operation returning the full flow definition as JSON, which implies no side effects. However, it does not cover error behavior, whether flowId is actually required despite the schema listing zero required parameters, or any permission requirements.

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 six words with no filler, front-loading the verb, resource, and output type. Every word contributes meaning.

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 one-parameter getter, the description plus schema is nearly sufficient: it names the resource and return type, and the parameter is self-evident. It could be stronger with an explicit note that flowId selects the flow and a pointer to list_flows for discovery, but there is no output schema or complex behavior requiring further explanation.

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 sole parameter, flowId, is self-explanatory and consistent with the tool name and description, so the agent can infer it identifies the flow. Although schema description coverage is 0% and the description does not explicitly mention flowId or its expected format, the parameter name carries enough meaning for this simple case.

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 a specific verb ('Get') and a specific resource ('full flow definition'), and states the return format as JSON. This distinguishes it from write tools like update_flow and list-style tools like list_flows, which would return summaries or perform mutations.

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 given for when to use this tool versus siblings such as list_flows, validate_flow, or update_flow. There is no mention of prerequisites, such as first obtaining a flowId from list_flows, and no exclusions are stated.

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