metadata_upsert_user_metadata

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

No annotations are provided, so the description carries the full burden. It does not disclose that without confirm:true the call returns a preview and does not execute (that key behavior lives only in the 'confirm' param schema), nor does it state that upsert overwrites existing metadata. The 'Tags: Metadata Controller' line is generated noise.

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?

Very short, but the content is mostly a raw HTTP path plus an auto-generated 'Tags:' line rather than purpose-built guidance. Nothing is front-loaded as a use case.

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 write tool with no annotations, no output schema, a nested free-form body and a confirm-gated preview mechanism, the description leaves almost everything about behavior and payload structure to be guessed.

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 33% and only the 'confirm' param is documented, but the description adds nothing about userId or the arbitrary body.metadata payload. With a nested, free-form metadata object whose semantics (keys, merge vs replace) are undocumented anywhere, this is a real gap.

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?

States a verb+resource ('Update or create User Metadata') plus a raw HTTP route for context. It doesn't differentiate from the sibling metadata_upsert_node_metadata or clarify what metadata means here, so it's clear but under-specified.

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 when-to-use guidance, no mention that siblings metadata_get_user_metadata / metadata_upsert_node_metadata exist or how to choose between them. The agent must infer the scope from the route string alone.

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