get_node_info

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

No annotations are provided, so the description must carry the full burden. It reveals the tool is a query (read-only) operation by mentioning 'Query' and states the return format. However, it does not explicitly state that there are no side effects, no state modifications, or potential error conditions, leaving some behavioral gaps.

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 extremely concise at two sentences. Every word is purposeful: the first sentence states the core action and return value, the second explains the optional filter. No redundant or extraneous 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 no output schema, the description adequately summarizes that the tool returns node inputs, outputs, and descriptions. It could mention error handling or endpoint availability, but for a simple read-only query, it is sufficiently complete for an agent to understand the tool's purpose and output.

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 input schema has 100% descriptive coverage for the single parameter, and the description merely echoes the schema's substring match explanation. It adds no new semantic meaning beyond what the schema already provides, so baseline score 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?

The description clearly states the tool queries ComfyUI's /object_info endpoint to get node type definitions, specifies optional filtering, and mentions the return type (node inputs, outputs, descriptions). The verb 'Query' and resource 'node type definitions' are specific and distinct from sibling tools like 'get_node_pack_details'.

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 explains the optional filter parameter but provides no guidance on when to use this tool versus alternatives, such as 'get_node_pack_details' or other info tools. It lacks explicit 'when to use' or 'when not to use' context.

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