telegram-get-boosts-status

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

Annotations already mark as read-only and open-world; description adds detailed behavioral context (what fields are returned, underlying API method). Does not contradict annotations. No mention of rate limits or side effects, but appropriate for a read-only tool.

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?

Very concise: front-loaded with purpose, then enumerates return fields in two sentences. No redundancy. Every sentence adds value.

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 simple read-only query tool with one parameter and comprehensive schema, the description fully explains what the tool does, what it returns, and its read-only nature. No gaps given available structured fields.

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 provides 100% description coverage for the single 'chat' parameter, explaining accepted formats. Description does not add additional parameter meaning beyond the 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?

Clearly states it fetches boost status of a channel/supergroup and lists returned fields. Distinguishes from siblings by specifically mentioning 'premium.GetBoostsStatus' and returns specific boost metrics, unlike get-my-boosts or get-boosts-list.

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?

Implies use for checking boost stats of a chat, but does not explicitly explain when to choose this over related tools like get-my-boosts (which retrieves user's own boosts) or get-boosts-list (lists boosters). No exclusion criteria provided.

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