search_nodes

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

The description discloses return limit (max 20 results) and the effect of includeExamples (top 2 template configs). The annotations already declare readOnlyHint and idempotentHint, so the tool is safe. The description adds useful behavioral details beyond annotations without contradiction.

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 concise (4 sentences) and front-loaded with the main action. Every sentence adds value: search purpose, parameter usage, limit, and examples option. No superfluous text.

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 6 parameters and no output schema, the description covers input usage well but lacks details on return format, sorting, or pagination beyond the limit. It is mostly complete for a search tool, but could mention whether results are sorted by relevance.

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% with descriptions for all parameters, so baseline is 3. The description provides a usage example for 'query' and paraphrases the intent of includeExamples, but adds minimal new semantic value beyond what the schema already offers.

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 it searches n8n nodes by keyword with optional examples. It distinguishes from sibling tools like 'get_node' (which retrieves a specific node) and 'search_templates' (which searches templates) by specifying that it searches nodes and can optionally include template configurations.

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 explicit usage instructions (e.g., 'Pass query as string. Example: query="webhook" or query="database".') and explains when to use optional parameters. However, it does not explicitly state when not to use this tool or list alternatives, but given the sibling context, the guidance is clear enough.

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