get_node_info

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

Description indicates the tool returns detailed info (type, parameters, inputs, outputs), implying a read operation. However, with no annotations, it does not explicitly state that the tool has no side effects, does not cook the node, or how errors are handled, leaving some behavioral ambiguity.

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?

Single sentence with no unnecessary words. It front-loads the verb and resource, and lists specific information categories, making it easy to scan.

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 and no output schema, the description offers a basic outline of returned data but omits parameter format details, return structure, and error cases. It is minimal but not fully inadequate for a simple getter.

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?

Input schema has one 'path' parameter with 0% description coverage, and the description does not describe the parameter format or meaning (e.g., absolute vs relative path, Houdini node path syntax). The tool's name and context imply 'path' refers to a node path, but this is not stated explicitly.

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?

Description uses specific verb 'Get' with resource 'node info', and enumerates the returned content: type, parameters, inputs, outputs. This clearly distinguishes it from siblings like get_node_doc or get_geo_summary.

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?

Description states what the tool does but provides no guidance on when to use it vs alternatives, no exclusions, and no use case examples. It leaves the decision entirely to the agent.

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