set_node_properties

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

With no annotations, the description must disclose behavioral consequences. It implies mutation but offers no details on whether properties are merged or replaced, whether the node must exist, or how errors and invalid inputs are handled. This is more than a tautology but still insufficient.

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 single sentence is front-loaded and free of fluff, but it is under-specified for a tool with an opaque properties object and no annotations. It is concise to the point of inadequacy rather than 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?

The tool has no annotations, no output schema, and an untyped nested properties object, so the description must compensate. It provides no context about supported property keys, mutation semantics, error behavior, or return values, leaving the agent without enough information to use the tool safely.

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 0%, and the description names no parameters. It does not define the expected format of 'path' or the structure of the 'properties' object, which is an untyped nested object. The description adds no parameter-level value beyond the 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 a mutating operation on a node's properties using a specific verb and resource. It is distinct from the sibling get_node_properties, but it does not clarify the scope of 'properties' or differentiate from related operations like rename_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?

No guidance is provided about when to use this tool versus alternatives. It does not mention prerequisites, relationships to add_node/delete_node, or exclusions for property types that may overlap with other tools.

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