List messages

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered by structured data. The description adds one genuinely useful behavioral fact — results come back newest first — but says nothing about pagination behavior, the meaning of a truncated result set, or rate limits on the chat endpoint.

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 sentence captures the operation and ordering, with zero padding. The trailing OCS endpoint line is debatable value for an agent that already has the tool, but it is short and does document the upstream surface.

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 simple read-only list operation with annotations covering safety and no output schema to explain, the description is close to adequate. The one meaningful gap is the pagination contract: without explaining limit and last_known_message_id, an agent cannot reliably fetch more than the first page of history.

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% and the description does not explain any of the three parameters. The embedded path 'chat/{token}' weakly hints that token identifies the conversation, but limit (default 50) and especially last_known_message_id — the pagination cursor — are left entirely undefined, and the interaction between a cursor and "newest first" ordering is genuinely ambiguous.

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?

"Read the chat history of one conversation, newest first" gives a specific verb (read), a specific resource (chat history of a single conversation), and an ordering guarantee. The "one conversation" scoping implicitly separates it from nextcloud_list_conversations, though no sibling is named explicitly.

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 intended use is implied by "read the chat history" — an agent knows to call this when it needs messages from a known conversation. There is no explicit statement of when NOT to use it, no hint about how to page through a long history, and no pointer to alternatives such as listing conversations first to discover the token.

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