Search across every chat

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

With readOnlyHint and openWorldHint already supplied, the description adds useful behavioral details: matches include their owning chat, results are newest first, date filters use unix seconds, and Telegram cursor overlap is removed and reported as skippedRepeat. These are real operational traits beyond the annotations.

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?

Four tightly packed sentences: scope first, then return behavior, then date filtering, then the pagination caveat. No filler and the important distinctions are front-loaded.

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 search tool with no output schema and annotations covering safety, the description usefully explains ordering, ownership, and deduplication. But the pagination parameters remain unexplained, leaving a gap in how an agent should page through results correctly.

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 must carry parameter meaning, but it only clarifies minDate/maxDate as unix-second window bounds. The query format, limit behavior, and especially offsetId/offsetRate pagination semantics are left entirely undocumented.

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 states a specific verb and resource: 'Full-text search over all chats at once'. It explicitly distinguishes this from a single-chat search with '(not one chat)', which is exactly the boundary an agent needs against sibling telegram_search_messages.

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?

It clearly establishes the global-search context and implicitly contrasts with per-chat search via '(not one chat)'. However, it does not name telegram_search_messages as the alternative, so the routing guidance is strong but not fully explicit.

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