Validate content receipts to fetch a verified preview and cache it locally. Supply a content ID to get an authenticated preview available for later access.
Fetch and locally cache a content preview after validating its receipts.
| Name | Required | Description | Default |
|---|---|---|---|
| content_id | Yes |
Changes observed during successful MCP inspections.
v0.6.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries full responsibility for behavioral disclosure. It does disclose a local-caching side effect and a receipt-validation precondition, which is more than the tool name implies. However, it never defines what 'receipts' are, what happens when validation fails, whether authentication or credits are involved, or what the returned payload looks like.
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 front-loaded 13-word sentence with zero filler: the verb 'Fetch' comes first and the qualifying behaviors follow in logical order. A sibling-disambiguation clause would have fit in the same space, so a perfect 5 is not warranted, but the structure is efficient.
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 no output schema and no annotations, the description is the agent's only source of behavioral information, yet it does not say what the tool returns, when receipt validation fails, or how this differs from rynmesh_fetch_preview. The local-vs-peer and preview-vs-full distinctions are critical in this sibling family, and 'receipts' is unexplained jargon, leaving the agent under-informed.
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%: the sole required parameter content_id has no schema-level documentation. The description adds nothing about the ID's format, origin, ownership, or constraints — an agent must guess whether it is a UUID, hash, or URL. The only weak link is that the tool name and description tie the parameter to 'content,' implying it identifies the content to preview.
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 names a specific verb and resource — 'Fetch and locally cache a content preview after validating its receipts' — and adds two distinguishing behaviors (caching and receipt validation) beyond a bare fetch. However, it does not differentiate this tool from near-identical siblings like rynmesh_fetch_preview, rynmesh_fetch_peer_content_preview, and rynmesh_fetch_peer_preview, all of which plausibly fetch previews.
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 or when-not-to-use guidance is provided, and no alternative tools are named. With roughly eight fetch-family siblings (local vs peer, preview vs full, bare vs content variant), an agent has no stated basis for choosing this tool over rynmesh_fetch_content_full or rynmesh_fetch_peer_content_preview. The only implied guidance is the word 'preview' itself.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.