remnawave_metadata_upsert_node

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

No annotations exist; description merely labels it a mutation without disclosing side effects, permissions, or specifics about behavior (e.g., whether it creates/updates, conflict handling).

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?

Extremely short, but under-specified to the point of being unhelpful. Not a model of conciseness; every sentence should add value.

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?

With 4 parameters, no output schema, and no annotations, the description fails to provide necessary context for correct invocation. Incomplete and insufficient.

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 coverage is 0% and description does not explain any of the 4 parameters (payload, confirmToken, responseMode, mutationApproved). The payload object's structure is entirely opaque.

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 states 'upsert_node (mutation)', which identifies the action and resource but does not clarify what upserting node metadata entails or how it differs from other node operations.

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 information on when to use this tool versus alternatives like remnawave_nodes_create or remnawave_metadata_get_node. No context or conditions provided.

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