rynmesh_download_relay_artifact

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

The description discloses a meaningful behavioral trait: the download is combined with hash verification. With no annotations provided, the description carries the burden, but it does not explain what happens on hash mismatch, whether destination is overwritten, or whether network access is required.

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?

The description is a single, front-loaded sentence with no filler. Every word contributes to understanding the tool's core operation.

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 simple download-and-verify tool, the core flow is conveyed. However, the optional relay_url remains unexplained, no output/return behavior is described, and there are no annotations to fill the safety or side-effect gaps.

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%, so the description must compensate. It adds meaning to content_hash by tying it to identity and verification, but it does not explain the destination parameter semantics or the optional relay_url parameter at all.

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 a specific verb ('Download'), a specific resource ('a relay artifact'), and the distinguishing mechanism ('by content hash'). It clearly differentiates this tool from siblings like rynmesh_upload_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?

The phrase 'by content hash' implies the agent should use this tool when it already has a content hash and wants to fetch the artifact. However, no explicit when-to-use or when-not-to-use guidance is given, and no alternative sibling is named.

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