n8n_get_workflow

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 successfully indicates the return content includes nodes, connections, and settings, but fails to disclose safety characteristics (read-only nature), error handling behavior, or rate limiting concerns.

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 consists of a single efficient sentence conveying the core purpose. However, the '[UNIFIED]' prefix appears to be implementation metadata that provides no value to the agent selecting the tool.

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 has only two parameters and no output schema, the description adequately explains what data is returned. However, it lacks critical parameter documentation and usage context that would make it fully complete for an 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 input schema has 0% description coverage for both required parameters (`site` and `workflow_id`). The description mentions 'specific workflow' implying the workflow_id parameter, but provides no semantics for the `site` parameter or format expectations for either value.

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 retrieves detailed workflow information, specifying the inclusion of nodes, connections, and settings. However, while it implies operation on a single workflow via 'specific workflow,' it does not explicitly differentiate this tool from the sibling `n8n_list_workflows` tool.

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 no guidance on when to select this tool versus alternatives such as `n8n_list_workflows` or `n8n_get_execution`. It omits prerequisites like obtaining the workflow_id from a prior list operation.

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