Get conversation messages

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It confirms the operation is read-only by saying 'Read', but it does not disclose ordering, pagination semantics, the meaning of `after`/`before`, or how the phone number identifies a conversation.

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?

The description is a single clear sentence with no waste. It front-loads the core action and object, making the purpose immediately readable.

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 low schema coverage, absence of annotations, and absence of an output schema, the description is too sparse. It should compensate by explaining the `phone`-to-conversation mapping, the meaning of `after`/`before`, and pagination behavior, especially because `pageSize` has no description.

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?

Only 25% of the parameters have schema descriptions, and the tool description adds no parameter-level meaning. `after`, `before`, and `pageSize` are left entirely to their schema types, and the description does not clarify how `phone` selects a conversation or how the temporal filters interact.

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 tool's action ('Read') and resource ('message history for a single conversation'), so an agent can tell this is a read-only message retrieval tool. It does not explicitly contrast it with the adjacent `gambot_list_conversations`, but the singular 'single conversation' plus 'messages' makes the core purpose specific enough.

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 description gives only a high-level purpose and no explicit guidance on when to use this tool versus alternatives such as `gambot_list_conversations` or the other `gambot_get_*` tools. It could be improved by noting, for example, that this Tool should be used when a conversation has already been identified and its full message history is needed.

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