conversations_mark

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

With no annotations, the description should disclose behavioral traits beyond what the name implies. It does not mention idempotency, side effects, or requirements (e.g., user membership in channel). The one-sentence description adds minimal transparency.

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?

While concise at one sentence, it is under-specified. The description is too brief to be informative, acting more as a placeholder than a helpful guide. It lacks structure and key details.

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 the tool's two required parameters and no parameter descriptions, the description is incomplete. It does not explain the ts parameter (likely a timestamp), the return value (though output schema exists), or the tool's behavior. The agent lacks sufficient information to use the tool correctly.

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 add meaning to parameters. It does not explain what 'channel' or 'ts' represent, their format, or how they relate to the action. The description fails to compensate for missing schema metadata.

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 clearly states the action ('Set the read cursor') and the resource ('in a channel'), which is specific and distinguishes it from sibling tools like conversations_history or conversations_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 is provided on when to use this tool versus alternatives, such as when to mark a channel as read versus using other conversations_* tools. The description lacks usage context.

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