metadata_upsert_node_metadata

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

With no annotations, the description carries the full disclosure burden, yet it only restates the HTTP method and a tag label. It never mentions that this is a non-GET operation requiring confirm:true (the tool returns a preview otherwise), nor any auth/permission requirement or what the upsert replaces versus merges.

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?

It is short and front-loads the endpoint, but the line 'Tags: Metadata Controller' is scaffolding noise that adds nothing for an agent. Overall brief rather than genuinely 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?

For a mutation tool with no annotations, no output schema, and a nested free-form body, the description omits critical behavior: the confirm/preview gate on non-GET calls, the shape of the metadata payload, and any error/response expectations. An agent could not call this correctly on the description alone.

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 only 33% (only 'confirm' is documented, and in Russian). The description adds no meaning for uuid or the free-form nested 'metadata' object, so it fails to compensate for the undocumented parameters, including what keys the metadata map accepts.

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 gives a specific verb ('Update or create') and resource ('Node Metadata') plus the concrete endpoint PUT /api/metadata/node/{uuid}. The node-vs-user distinction is implicit in the name and path, and siblings metadata_upsert_user_metadata / metadata_get_node_metadata make the target clear, though the description never states the differentiation itself.

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 over metadata_get_node_metadata or metadata_upsert_user_metadata, nor any prerequisite/context. The only routing signal is the HTTP verb embedded in the raw path.

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