get_channel_posts

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

No annotations are provided, so the description carries full burden for behavioral transparency. It mentions 'latest posts with view metrics' but does not clarify ordering, pagination behavior, error handling (e.g., invalid channel), or that it is a read-only operation. This is insufficient for a tool with no 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 concise sentence that front-loads the core functionality. It could be improved by adding more useful details (e.g., default limit value) without increasing length significantly.

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 absence of an output schema, the description should at least hint at the return structure (e.g., fields like post text, view count). It mentions 'view metrics' but does not specify what metrics or how they are presented. For a simple tool with 3 parameters, the description is somewhat incomplete.

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 input schema already provides descriptions for all three parameters (channel_id, limit, offset), achieving 100% schema description coverage. The tool description adds no additional meaning beyond the schema, so the baseline score of 3 is appropriate.

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 retrieves the latest posts of a Telegram channel with view metrics. It uses a specific verb (get) and resource (channel posts), and implicitly distinguishes from siblings like get_post (single post) and search_posts (search).

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?

No explicit usage guidelines or when-not-to-use scenarios are provided. The description implies basic usage for fetching recent posts, but does not discuss alternatives or contexts where other tools (e.g., get_channel_stats or search_posts) might be more appropriate.

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