get_telegram_tracker

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

With no annotations, the description carries the transparency burden. It discloses that the tool aggregates data from 50 channels, offers a curated offline database, and supports optional live tracking via Telethon setup. It reveals dependencies (pip install, API credentials) and the comparison dimensions. While it doesn't mention data freshness or error handling, the provided behavioral depth exceeds a bare minimum.

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 somewhat verbose, including a marketing quote ('I tracked 50 Indian stock tip channels for 30 days — here's which ones are scamming you') that adds no functional value. However, the structure is organized with a clear purpose statement, setup notes, and an Args section, making it navigable despite the extra length.

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?

The tool is simple (one optional parameter, output schema present), and the description covers key aspects: what it compares, the channel input, the curated database, and live tracking prerequisites. It doesn't mention invalid channel handling or output format, but these are partially covered by the output schema and overall simplicity. The description is sufficiently complete for agent 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?

The single parameter `channel` is fully explained in the description: it gives an example handle ('@NSEBSEtips') and clarifies that leaving it empty returns the full comparison database. Since the schema has no per-property description (0% coverage), the description fully compensates with valuable 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?

The description clearly states it is a 'Dalal Street Telegram signal tracker' that compares 50 public Indian stock tip channels by accuracy, return, and pump-and-dump probability. This specific verb and resource, combined with its unique focus on Telegram social signals, distinguishes it well from the many market-data sibling tools.

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 implies usage through 'Works out of the box' and explains the channel parameter ('Leave empty for full comparison database'). However, it does not explicitly state when to prefer this tool over alternatives or provide exclusion criteria. The setup instructions for live tracking add context but do not fully guide tool selection.

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