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

Annotations already declare readOnlyHint, destructiveHint false, and openWorldHint false, so 'Read-only' is largely redundant. The description does add genuinely new behavioral detail: ordering (newest first) and that each item carries its conversationId, but says nothing about page size or what happens when the list ends.

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 compact sentence, front-loaded with the resource and scope, with ordering stated before the trailing safety note. The final 'Read-only' clause duplicates annotations and is the only wasted element.

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, the description helpfully discloses that entries are already ordered and expose conversationId, which is the key field an agent needs for the next call. For a single-optional-parameter list tool with full annotation coverage, that is close to sufficient; only pagination behavior is unaddressed.

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 coverage is 100% and the single cursor parameter is already fully documented in the schema. The description adds no pagination semantics beyond what the schema provides, so baseline 3 applies.

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 (the user's chats with the OsmO assistant in the OsmO app) and names the payload element (conversationId), which implicitly separates it from the singular get_chat. It does not explicitly name an alternative tool, so it stops short of a 5.

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 listing scope and 'newest first' ordering imply the read-all use case, and mentioning conversationId hints that get_chat is the follow-up. But there is no explicit when-to-use versus get_chat or sibling lists, and no stated exclusions.

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