rynmesh_relay_artifact_info

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

With no annotations provided, the description carries the full burden of behavioral disclosure. The verb 'Read' implies a non-mutating operation, but the description does not explain whether this is a network call, whether authentication is needed, what failure modes exist, or what kind of metadata is returned.

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 concise sentence with the action verb front-loaded. It contains no redundant words, though the term 'relay metadata' is somewhat jargon-heavy and could have been slightly more explicit.

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 tool with undocumented parameters, no output schema, and no annotations, the description is too thin to fully guide an agent. It does not clarify the role of relay_url, the shape of the returned metadata, or any preconditions for calling the tool successfully.

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. The phrase 'content-addressed artifact' gives a hint that content_hash is the identifier, but relay_url is left completely unexplained, including why it is optional and how it affects the lookup.

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 ('Read') and a specific resource ('relay metadata for a content-addressed artifact'). This clearly distinguishes it from sibling tools like rynmesh_download_relay_artifact and rynmesh_upload_relay_artifact, which transfer content rather than read metadata.

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 about when to use this tool versus alternatives. It implicitly suggests a read/metadata use case, but it does not mention related siblings such as download/upload relay artifact or other info tools, nor does it state when this would be the preferred choice.

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