get_node_info

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

With no annotations provided, the description fully covers behavioral traits: requires a reachable instance, returns results specific to that server, and details the summarized list behavior when more than 20 nodes match. This goes beyond basic read-only semantics.

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?

Description is concise with no redundant information. Front-loaded with the primary action, then covers filtering behavior and the edge case of >20 results. Every sentence adds value.

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 tool with one parameter, no output schema, and no annotations, the description is complete. It explains the endpoint, prerequisites, filtering, and the summarized list behavior. No gaps for the intended use.

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 single parameter 'node_type' is well-documented in both schema and description. The description adds usage context ('inspect a specific node before composing or modifying a workflow'), which is value beyond the schema's substring match explanation.

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?

Clearly states the tool queries a ComfyUI server's /object_info endpoint for node type definitions, including inputs, outputs, category, and description. The verb 'query' and specific resource distinguish it from sibling tools that list installed nodes or API nodes.

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 explicit when-to-use advice: inspect a specific node before composing/modifying a workflow. Describes the requirement of a reachable ComfyUI instance and the filtering behavior. No explicit when-not or alternative tools, but the filtering guidance is helpful.

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