list_node_templates

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

Without annotations, the description carries the full burden. It discloses the default filtering behavior (only templates with images), the side effect of the include_without_images parameter changing result set content, and the extracted vendor label limitation (best-effort, not an API field). This is thorough and accurate.

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 efficient, with a concise main sentence and a bullet for the parameter. It front-loads the key action (listing templates with vendor context). The one extra detail about the vendor label extraction is valuable but slightly elongates the description. Still, very well-structured.

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 tool's simplicity (one optional boolean parameter, no complex output), the description fully clarifies behavior, default filtering, parameter use, and data provenance for the vendor field. No gaps remain; the agent can confidently use this tool.

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 0%, so the description must compensate for the undocumented include_without_images parameter. It does so excellently, explaining both that passing true shows the full catalog (including templates without images) and that those templates cannot be used to add a node, adding meaning far beyond the schema's title and default.

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 lists node templates with vendor context, specifying that by default only templates with installed images are shown. The mention of the best-effort vendor label extracted from the description adds precision, and the tool is easily distinguished from siblings like list_node_templates (singular) or other list_ functions.

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 explicit guidance on when to use the include_without_images parameter, explaining that by default only usable templates are listed and passing true reveals the full catalog, including those that cannot be used to add a node. This helps the agent decide when a broader view is needed.

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