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

Annotations already cover the mutation/idempotency/open-world profile, and the description adds real value beyond them: creation of NEW flows (non-destructive), no AI call, a 25-workflow limit, and a precise account of how source nodes map to target node types. It does not address failure behavior or required n8n connection state, keeping it short of a 5.

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?

Purpose is front-loaded, followed by a dense but informative mapping sentence, then the limit and the id-source hint. The mapping enumeration is long yet earns its place by telling the agent what the import will produce.

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 4-param, fully-documented tool with no output schema, the description covers purpose, transformation semantics, limits, and the ID prerequisite. It is complete enough to invoke confidently; only failure/rollback and connection prerequisites are unaddressed.

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 all four parameters are already documented, including the 'up to 25' limit and the list_n8n_workflows provenance. The description restates rather than extends that, so the baseline 3 applies.

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?

States a specific verb (map/import) and resource (n8n workflows into new Wavelength flows), and immediately distinguishes itself from AI-based creation with 'with no AI call'. The detailed node-mapping sentence makes the transformation concrete, setting it apart from siblings like import_dbt_lineage or import_from_google_drive.

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?

Provides an explicit prerequisite ('Get ids from list_n8n_workflows') and a hard cap ('Up to 25 workflows per call'). It does not spell out when NOT to use this tool or name the AI-alternative sibling (e.g. create_flow_from_text), so guidance is clear but not fully exclusive.

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