search_telegram

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

The description mentions using Telethon and required tokens, which adds behavioral context. But without annotations, it lacks details on safety, destructiveness, or rate limits. Moderate transparency.

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 adequately structured with sections but is somewhat verbose. Could be more concise by removing redundant docstring formatting.

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 across channels, the description includes return format and prerequisites but misses error handling specifics or pagination details. Sufficient but not complete.

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?

Despite 0% schema coverage via structured descriptions, the docstring in the description explains query and max_results with purpose and range, adding value beyond the schema's type/title.

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 'Search messages across all available Telegram channels' with a specific verb (search) and resource (Telegram channels), and the tool name distinguishes it from siblings like search_telegram_channel.

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?

Usage contexts are given: 'monitoring channels, searching discussions, gathering topic information.' However, no explicit exclusion or comparison to sibling tools is provided.

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