comfyui_get_object_info

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

Annotations already indicate readOnlyHint=true and idempotentHint=true. The description adds value by specifying the exact API endpoints ('/object_info' and '/object_info/{node_class}'), which provides structural context beyond the annotations. No contradictions.

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 a single, front-loaded sentence with no wasted words. It efficiently conveys the core functionality.

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 simple nature of the tool (one optional parameter, read-only, idempotent) and the presence of annotations and an output schema, the description is complete enough. It covers the primary behavior and the endpoint structure.

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 description does not expand on the parameter 'node_class' beyond what the input schema's description already provides ('Optional node class name. If omitted, returns all node definitions.'). With 0% description coverage in the tool text, the baseline of 3 applies as the schema carries the meaning.

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 'Fetch node metadata from `/object_info` or `/object_info/{node_class}`' clearly states the action (fetch) and the resource (node metadata), and it distinguishes this tool from siblings like comfyui_get_features or comfyui_list_models by specifying node object info.

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 does not provide explicit guidance on when to use this tool versus alternatives. While the name and endpoint imply usage for node metadata, there is no statement of prerequisites, contexts, or when not to use it, which is a gap given the number of sibling get tools.

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