telemost_messages

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds valuable context beyond this by specifying public-channel scope, the optional `since` date filter, and payment via USDC (billing behavior). This goes beyond simply restating 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?

The description is compact and front-loaded: the first sentence states the core function. The second sentence gives use cases, and the third covers filtering and payment. Every sentence earns its place with no fluff or repetition.

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 has 3 parameters with no descriptions and no output schema. The description covers purpose, use cases, `since`, and pricing, but omits semantics for `source` and `region`, and does not describe return format or pagination. This is adequate but has clear gaps.

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 explain parameters. It does clarify `since` ('filters by date'), but it gives no guidance on `source` (format, required, what counts as a channel/group) or `region` (meaning of 'cis' vs 'worldwide'). Description only compensates for one of three parameters.

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's function: 'fetch recent messages and posts from any public Telegram channel or group.' This uses a specific verb ('fetch') and resource ('Telegram channel/group'), and it distinguishes itself from siblings like telemost_post (single post) and telemost_posts_search (search) by emphasizing recency and monitoring.

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 provides clear use contexts: 'Monitor news sources, track updates, or feed content into downstream analysis.' This implies when to use the tool, but it does not explicitly mention alternatives or when-not-to-use, so it stops short of a 5.

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