telemost_compilations

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds key behavioral context beyond that: the call is paid per use in USDC, and the data is curated and organized by theme. This is valuable and does not contradict 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 a single, front-loaded sentence that conveys purpose, use case, and cost structure without wasted words. The parenthetical about pricing is useful and concisely integrated.

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 tool with no parameters and good annotations, the description covers purpose, usage context, and cost. However, it does not describe what a 'compilation' looks like in the response (e.g., list of channel names, metadata), and there is no output schema to fill that gap.

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 tool has 0 parameters, so the baseline is 4. There is no parameter information needed; the schema already covers 100% of the (empty) parameter set, and the description adds nothing that would conflict with it.

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 provides curated compilations of Telegram channels for discovery and research, which distinguishes it from sibling tools like telemost_search or telemost_catalog. However, it does not use a verb like 'get' or 'list' and the differentiation is implicit rather than explicit.

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 market mapping and research, giving a clear context. It does not explicitly say when not to use it or name an alternative tool for related tasks, and the mention of telemost_catalog is only for pricing, not for choosing the right tool.

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