Call node method

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

Annotations indicate destructiveHint=true and openWorldHint=true. The description's 'escape hatch' label and destructive example (.destroy()) reinforce the risk. It could be more explicit about potential side effects, but overall complements annotations well.

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 purpose and usage guidelines. No extraneous words. Highly efficient.

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?

Complex tool with arbitrary method invocation. Description covers purpose, usage boundaries, and examples. No output schema, but returns are method-dependent. Could mention error handling, but not essential given the open-ended nature.

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 100% description coverage, so parameters are documented. The description adds minimal value beyond examples of method names. No clarification on path format or args/kwargs usage beyond schema.

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 arbitrary Python methods on nodes, positioning itself as an escape hatch. It distinguishes from other tools by specifying it should be used only when structured tools are insufficient. Examples like .cook(), .copy(), and .destroy() clarify the scope.

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 advises preferring structured tools and reserving this for uncovered operations. This provides clear selection criteria and context, making it easy for an agent to decide when to use this tool.

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