n8n_search_nodes

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

Annotations already mark this as readOnlyHint=true, so the safety profile is covered. The description adds useful behavioral context: the tool returns summaries, searches the full catalog, and serves as a precursor to n8n_get_node. It does not detail result structure or pagination, but for a read-only search tool the added context is meaningfully beyond the annotations.

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?

Three sentences, no filler, and the most important facts come first: what the tool searches, when to use it, and how it relates to n8n_get_node. Every sentence earns its place.

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?

This is a simple two-parameter read-only search tool. The description covers its purpose, catalog size, usage context, return type (summaries), and the related tool for full schemas. Nothing material is missing for an agent to select and invoke it correctly.

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 description coverage is 100%, so both 'query' and 'limit' are already documented with descriptions and examples. The description adds context about the catalog and result type but no new parameter-level detail, so the 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?

States a specific verb ('Search'), a precise resource ('the full catalog of 560 n8n nodes'), and its source ('extracted from the real n8n packages'). It also differentiates itself from the sibling n8n_get_node by noting it returns summaries rather than full parameter schemas, so an agent can distinguish the two tools immediately.

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?

Explicitly tells the agent when to use it: 'Use this BEFORE creating a workflow so node types are correct.' It also names the alternative for deeper detail ('use n8n_get_node for the full parameter schema'), giving both timing and a clear decision boundary.

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