bale_get_dialogs

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

With no annotations, the description carries the full burden. It usefully discloses the payload (resolved titles, unread counts, last messages) and 'Retrieve' signals a read operation, but it says nothing about authentication requirements, whether results are paginated, or what offset_date does behaviorally. Partial disclosure only.

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 tight sentence with the resource and return content front-loaded. No filler, though it is arguably too short given the undocumented parameters.

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-shape explanation is not required, but the 4 undocumented parameters and absent annotation/usage context leave real gaps for correct invocation (pagination via limit/offset_date, pinned filtering). The description is not sufficient for the tool's parameter surface.

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% across 4 parameters, so the description must compensate and largely does not. Only 'resolved' loosely hints at resolve_titles; limit, offset_date, and exclude_pinned are never explained in either place, leaving the agent guessing at pagination semantics.

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 ('Retrieve') and resource ('recent chats, groups, and channels') plus the returned fields (resolved titles, unread counts, last messages). This clearly distinguishes it from bale_get_chat_history and the mutation siblings, though it never explicitly contrasts with the closest sibling bale_search_dialogs.

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 guidance on when to use this versus bale_search_dialogs or bale_list_sessions, nor any mention of prerequisites such as an authenticated session. The 'recent' framing implies a browsing use case, but nothing is stated explicitly.

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