get_messages

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

With no annotations, the description carries the burden and does well: it discloses ordering, default date window, timezone handling, offset semantics, and return fields. However, it omits the `limit` parameter entirely, and the opening 'up to 200' may mislead given the schema default of 50.

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?

Front-loaded with a clear summary, followed by compact parameter explanations and a return-field list. Every sentence adds relevant information; no fluff.

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?

Rich enough for a read-only messaging tool, especially with output schema present. The main gap is the undocumented `limit` parameter and its relationship to the 'up to 200' claim, which an agent needs to select the right invocation.

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?

At 0% schema description coverage, the description must compensate. It clearly explains chat, since_date, and offet_id, including formats and defaults. The `limit` parameter is missing, so one of four parameters remains semantically unexplained.

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 operation (get messages), the resource (one chat), the quantity/ordering (up to 200, newest first), and implicitly distinguishes from siblings like search_messages and list_dialogs. The scope 'from one chat' makes its role clear.

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?

Provides clear usage context: retrieve recent messages from a single chat, with a default 7-day window and offset-based pagination. It does not explicitly mention alternatives such as search_messages, but the 'one chat' scope and cross-reference to get_channel_info give sufficient guidance.

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