inspect_node_type

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

Annotations declare readOnlyHint=true and openWorldHint=false, and the description's 'Inspect' verb aligns with a safe read operation - no contradiction. The phrase 'complete native ComfyUI schema' adds modest context about the scope of what is returned. However, it doesn't describe output volume, error behavior for invalid class types, or whether the full schema is returned as structured JSON, so the value added beyond annotations is limited.

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?

A single, tightly worded sentence with zero waste. The action and object are front-loaded with no filler or redundancy. Every word 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?

For a simple one-parameter, read-only inspection tool with no output schema, the definition is borderline adequate. It clearly states what it does and the annotation covers the safety profile, but it leaves the agent to guess what class_type should contain and offers no usage guidance. Given the tool's low complexity and the sibling overlap, this is a minimum-viable definition that could be more complete.

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 0%, so the description carries the full burden of explaining the parameter. The phrase 'one installed node type' weakly hints that class_type names a node type, but it never explicitly maps class_type to that concept, states its expected format, or notes that it must be an installed node type identifier. The description insufficiently compensates for the zero coverage.

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 uses a specific verb ('Inspect') and identifies a clear resource ('the complete native ComfyUI schema for one installed node type'). This distinguishes it from siblings like inspect_canvas (canvas vs node type) and search_nodes (search vs inspect), though it doesn't name them explicitly. A 5 would require explicit sibling differentiation, so 4 is appropriate.

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 no guidance on when to use this tool versus alternatives like search_nodes or inspect_canvas, and no prerequisites or exclusions are stated. The usage context is only implied by the purpose clause, so the agent receives no routing help.

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