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

The description adds no behavioral detail beyond the operation itself: no pagination semantics for beforeSequence, no result-cap behavior for limit, no auth/permission notes, no statement about what a search does or does not cover. It also conflicts with the annotations, which set readOnlyHint=false while the description presents this as a pure read/search operation.

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?

A single front-loaded sentence with no filler; the scope constraint lands immediately. It is efficient, though its brevity contributes to the documentation gaps elsewhere rather than being a virtue on its own.

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?

An output schema exists, so return values need not be explained, but with four parameters at 0% schema description coverage the description leaves pagination and search semantics undocumented, and it does not address the readOnlyHint=false signal. For a tool whose only required input is a UUID the agent must already have, this is too thin.

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 carries the full burden, yet it only loosely implies conversationId ('inside one conversation') and query ('search'). It says nothing about limit (max 100), beforeSequence as a pagination cursor, or what fields the query matches against.

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 gives a specific verb pair (read/search) plus the resource (message history) and constrains scope to 'one conversation belonging to the connected user', which is more precise than the title 'Read my 引力AI messages'. It is clearly distinguishable from fitmeet_conversations_list (which enumerates conversations), but it never names a sibling, 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?

There is no when-to-use guidance, no when-not-to-use, and no routing to alternatives such as fitmeet_conversations_list for discovering the conversationId first. Nothing tells the agent when to supply a search query versus walking history with beforeSequence, so usage must be inferred from the schema alone.

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