metadata_node_upsert

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

Annotations already establish that this is a non-destructive mutation (readOnlyHint=false, destructiveHint=false). The description adds nothing beyond that: it does not say whether metadata is merged or replaced, what happens to existing keys, whether partial objects are allowed, or what the call returns. No contradiction, but no added behavioral value.

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?

Five words, front-loaded verb and resource, no filler. It is efficiently written, though the brevity reflects under-specification rather than tight editing of a richer statement.

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 a mutation tool taking a nested free-form object with 0% schema coverage and no output schema, the description omits everything an agent needs: merge semantics, target node identity, and the metadata contract. It is not remotely complete.

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 contributes nothing about either parameter. The agent gets no explanation of what 'uuid' identifies (a node), nor any hint about the shape or semantics of the free-form 'metadata' object, which is the tool's entire payload.

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 decodes the name's 'upsert' into 'Update or create' and names the resource (Node Metadata), so the operation is intelligible. However, it is essentially a restatement of the tool name with no distinguishing detail against siblings like metadata_node_get or metadata_user_upsert, so it sits at the vague/tautological boundary.

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?

There is no guidance on when to use this versus metadata_node_get or when an upsert is preferable to a plain update. The agent must infer the context entirely from the name.

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