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

The readOnlyHint annotation already establishes this as a safe read. The description adds only the raw REST verb/path ('GET /conversations/{slug}'), with no mention of failure behavior, auth requirements, or what a missing slug yields. With annotations carrying the safety profile, this is thin added context.

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?

Two short sentences with the primary action front-loaded and no filler. The REST endpoint note is compact and useful for mapping to the upstream API.

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 single-identifier read tool with annotations covering safety and a fully documented parameter, the description supplies what an agent needs to invoke it. Absent an output schema, it could optionally hint at the returned conversation shape, but that gap is minor here.

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?

Single required parameter with 100% schema description coverage, so the schema already defines 'slug' as the conversation slug. The description repeats only that the lookup is by slug, matching the baseline for schemas that do the heavy lifting.

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 specific verb and resource ('Get a single conversation') plus the retrieval key ('by its slug'), and the word 'single' implicitly distinguishes it from reamaze_list_conversations. It stops short of naming the sibling explicitly, so it lands just under the top band.

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 explicit when-to-use or when-not-to-use guidance and no named alternatives, but the combination of 'single' plus a required slug implies the lookup-by-identifier use case versus the list tool. The agent must infer the routing rather than read it.

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