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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the prerequisite that voice_map entries need real voices from find_voices, which is genuinely useful context, but it otherwise restates return contents that the output schema already carries.

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?

Three tight sentences with no filler, and the no-argument versus with-argument split is front-loaded. The leading sentence is a verbless fragment, which slightly hurts readability but not economy.

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?

With an output schema present, return values need not be explained, and the description covers both invocation modes plus the find_voices prerequisite. Nothing critical is missing for an agent to call this correctly.

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 100% and the single node_type parameter is already documented in the schema. The description's note that omitting it lists every type adds marginal semantic value over the schema's 'Omit to list every type first', so the baseline 3 is appropriate.

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 names the resource precisely (node types, a node's config_schema, inputs and outputs) and distinguishes its two modes by argument presence. It is specific enough to separate from siblings like list_providers or validate_workflow_definition, though the opening fragment 'The node types you can use' lacks a clear verb and reads elliptically.

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?

It gives explicit when-to-use guidance for each mode: omit the argument to enumerate types first, pass node_type to get the schema. It also states a prerequisite ('read it before writing its config') and routes to the sibling find_voices when a generator's voice_map is involved.

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