Resolve Node

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

No annotations are provided, so the description carries full burden. It states it 'returns matching nodes' but does not disclose read-only nature, authentication requirements, or rate limits. For a search tool, more behavioral context (e.g., 'read-only lookup') is needed.

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?

Two sentences, no filler. Each sentence serves a purpose: first states action and input, second states output. Efficient and front-loaded.

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 of a search tool and absence of output schema, the description adequately describes the output ('IDs, types, and flow context') but lacks detail on format (e.g., array of objects). Still fairly complete for the tool's simplicity.

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 the base is 3. The description adds minor context ('using the node registry') but does not add meaning beyond the schema's parameter descriptions. The description's mention of 'name, type, or description' aligns with the schema.

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 verb 'look up', the resource 'node IDs', and the scope 'by name, type, or description'. It distinguishes from sibling tools like node-red-nodes-list (list all) and node-red-graph-query (query graph) by focusing on resolving based on registry attributes.

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 implies usage for looking up node IDs but does not explicitly state when to use this tool over alternatives like node-red-nodes-list or node-red-graph-query. No exclusions or when-not-to-use guidance is provided.

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