rynmesh_upload_relay_artifact

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

No annotations exist, so the description must carry the transparency burden. It reveals only that bytes are content-addressed, but says nothing about deduplication/overwrite, hash verification, authorization, network effects, or what happens on failure.

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?

One terse sentence with no filler; the action and destination are front-loaded. It is appropriately compact for what it states.

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?

Given five undocumented parameters, no output schema, and no annotations, the detail is insufficient: the agent cannot know what to provide for filename/media_type/expected_hash or what the upload returns.

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?

With 0% schema description coverage, the description must explain the parameters, but it only weakly maps 'local artifact' to path and 'configured relay' to relay_url. filename, media_type, expected_hash, and relay_url semantics remain unexplained.

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 opens with the verb 'Upload' and names both resource ('local artifact') and destination ('configured relay'), plus the addressing mode ('content-addressed bytes'), making the operation unambiguous. This clearly separates it from siblings like rynmesh_download_relay_artifact and rynmesh_relay_artifact_info.

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 on when to choose this over sibling upload/publish tools, or under what circumstances relay configuration is required. The only clue is the word 'configured,' but no alternative tools or exclusion conditions are named.

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