Call node method

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true. The description adds the 'escape hatch' framing and example methods including .destroy(), but does not detail potential side effects, failure modes, or return behavior—though these are inherently unpredictable for arbitrary method calls.

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?

Two sentences, front-loaded with the core purpose, and every clause earns its place. The 'Escape hatch' opener immediately signals the tool's nature and appropriate usage.

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 an escape-hatch tool with open-world semantics, the description covers what it does, when to use it, and why. There is no output schema, and return values are inherently method-dependent, so the description is reasonably complete for this class of 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 description coverage is 100%, with all four parameters documented. The description adds example method names but does not meaningfully go beyond the schema's own description of 'method' and the positional/keyword argument arrays.

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 invokes an arbitrary Python method on a node (operator), framing it as an escape hatch. It distinguishes from structured siblings by positioning this as the fallback for operations they don't cover, with concrete examples.

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?

Explicitly instructs to prefer structured tools when one exists and to use this only for operations they don't cover. Provides concrete examples (.cook(), .copy(), .destroy()) and sets context as a last-resort tool.

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