get_node_types

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

With no annotations, the description must convey behavior. It discloses that default returns minimal info and that 'fields' can provide more, which is useful. However, it omits details about pagination, limits, or any side effects, leaving gaps in transparency.

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 two concise sentences (14 words) with no redundancy. The first sentence immediately states the purpose, and both sentences serve a clear function.

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?

The description explains the default vs. detailed output but does not mention the 'search' or 'category' parameters, nor does it specify what the minimal info includes. Since there is no output schema, more detail on return structure would aid completeness.

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 coverage is 100%, so baseline is 3. The description adds 'Use 'fields' for more details,' which reiterates the parameter's purpose but adds little beyond the schema's own description. No value added for 'search' or 'category' parameters.

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 states 'Search available node types.' This clearly identifies the tool's action (search) and resource (node types), distinguishing it from siblings like 'get_node_info' (specific node) and 'search_custom_nodes' (custom 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?

The description provides implicit usage guidance via 'Use 'fields' for more details,' but does not explicitly state when to use this tool versus alternatives or when not to use it. No exclusions or sibling comparisons are given.

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