set_node

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

Discloses merge semantics, error-if-not-exists behavior, concurrency guards, return value, and persistence, with no annotations to rely on.

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?

Dense but efficient; every sentence adds value. Slightly long but justified by complexity.

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?

Covers all aspects: purpose, parameters (including nested object), behavioral rules, error conditions, sibling differentiation, and return values, despite no output schema.

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?

Provides full context for all 5 parameters despite 0% schema coverage: explains path format, set merge rules, create flag, baseRev/force concurrency, and error behavior.

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?

Clearly identifies the tool as a shorthand to patch a single node by path, distinguishing it from siblings like edit_board and get_node.

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 states when to use (single card edit) and when not (edges, deletes, multiple cards: use edit_board), plus details on creation and concurrency.

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