get_telegram_tracker

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

No annotations are provided, so the description carries the full burden. It indicates the tool is a comparison (read-only) operation and mentions live tracking as an enhancement, but does not disclose potential side effects, authentication requirements for the base database, or data freshness. The behavioral traits are adequate but not fully transparent.

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 includes a front-loaded purpose and inline argument documentation, but contains a verbose tweet-like quote ('I tracked 50 Indian stock tip channels for 30 days...') that adds little value and increases length. While efficient in parts, the fluff reduces conciseness.

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?

Given the tool's simplicity (one optional parameter, no required params, output schema provided), the description covers the key usage scenarios, parameter behavior, and optional live tracking setup. It lacks error handling details or data freshness notes, but is largely complete for an agent to invoke 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%, and the description fully compensates by explaining the only parameter 'channel': it specifies the format (handle with @, e.g., '@NSEBSEtips') and the behavior when left empty (full comparison database). This adds complete meaning beyond the schema's default and type.

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 identifies the tool as a Telegram signal tracker that compares 50 Indian stock tip channels by accuracy, average return, and pump-and-dump probability. This verb+resource definition is specific and distinguishes it from sibling tools like 'get_signal_accuracy' or 'detect_pump', which focus on different aspects.

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 for comparing Telegram stock tips and provides optional live tracking setup, but lacks explicit guidance on when to use this tool versus alternatives. It does not mention when not to use it or scenarios where another tool would be better, such as for individual signal analysis.

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