analyze_n8n_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 mentions analysis and optimization but doesn't describe what the tool actually does behaviorally: Does it return suggestions? Generate reports? Modify the workflow? What are the performance characteristics or limitations? The 'SAVES' hint about 'Claude context for strategic decisions' is vague and doesn't clarify the tool's behavior. This leaves significant gaps in understanding how the tool operates.

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 uses a bulleted format with sections (WORKFLOW, TIP, SAVES) which provides some structure. However, it's somewhat verbose with marketing-like language ('Perfect for understanding complex code') that doesn't add concrete value. The 'SAVES' section is particularly vague and doesn't clearly explain tool behavior. While not excessively long, some sentences don't earn their place in helping an agent understand 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 complexity (12 parameters, nested objects) and absence of both annotations and output schema, the description is insufficiently complete. It doesn't explain what the tool returns, how optimizations are suggested, what format results come in, or any behavioral constraints. For a tool with this many parameters and no structured output documentation, the description should provide more complete context about the tool's operation and results.

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 100% description coverage, so all parameters are documented in the schema itself. The tool description doesn't add any meaningful parameter semantics beyond what's already in the schema. It mentions 'n8n workflow JSON' which corresponds to the 'workflow' parameter, but this is already clear from the schema. With complete schema coverage, the baseline score of 3 is appropriate as the description doesn't enhance parameter understanding.

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's purpose: 'Analyze and optimize n8n workflow JSON for efficiency, error handling, and best practices.' This specifies the verb (analyze/optimize), resource (n8n workflow JSON), and scope (efficiency, error handling, best practices). However, it doesn't explicitly differentiate from sibling tools like 'analyze_code_quality' or 'analyze_single_file' which might have overlapping functionality.

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 some usage context in the 'TIP' section: 'Use Desktop Commander to read files, then pass content here for analysis.' This implies a workflow but doesn't explicitly state when to use this tool versus alternatives like 'analyze_single_file' or 'analyze_project_structure.' The 'WORKFLOW' section suggests it's for 'understanding complex code, identifying issues, and technical debt assessment' but doesn't provide clear exclusions or comparisons to siblings.

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