telegram_watchlist

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

No annotations provided, so description conveys the tool's behavior well: returns mentions and summaries, not technical data. Could mention data freshness or permissions, but sufficient.

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?

Concise and well-structured: purpose first, then usage guidance, exclusions, alternatives, and parameter. No unnecessary words.

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?

Covers purpose, usage, and parameter. With output schema existing, it is fairly complete, though could elaborate on output content.

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 coverage is 0%, but description includes parameter explanation: 'hours: 집계 시간 범위(시간). 기본 24.' Adds value beyond empty schema.

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 the tool returns how watched stocks are discussed on Telegram, with original texts and summaries. It differentiates from sibling tools by specifying it does not provide technical indicators, only Telegram mentions.

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?

Explicitly mentions when to call (e.g., for opinions, news, 'how is it' requests) and when not to (technical indicators). Directs to StockLens for indicators and notes stock registration via Telegram commands.

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