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

With no annotations provided, the description carries the full behavioral burden. It transparently states that this is a full-text search over a public catalog, requires no Telegram account, returns counts/categories/trust scores, and will find communities the user has not joined. It could mention output shape or sorting, but the disclosed behavior is solid for a read-only search 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?

Three tight sentences, front-loaded with the core purpose and scale, followed by the no-account differentiator and a guidance hint about type. Every sentence adds value and no words are wasted.

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 3-parameter tool with no output schema and no annotations, the description is nearly complete: it explains what is searched, what data is returned, and a key behavioral caveat (no Telegram account needed). Minor gaps like default sorting or pagination behavior are not critical for selection.

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 100%, so the schema already documents query, type, and limit. The description adds useful context by explaining the catalog scope and the effect of type, but it does not meaningfully extend the parameter semantics beyond what the schema already states.

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 opens with 'Full-text search over the tgden catalog', naming a specific verb, resource, and entity kinds, and immediately distinguishes itself from siblings like best_channels_by_category or search_posts. The mention of channels, chats, and bots makes the scope 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 gives clear usage context: it searches the public catalog without a Telegram account and is suitable for finding communities the user has NOT joined. It advises using type to constrain the entity kind, but it does not explicitly state when to prefer or avoid this tool relative to siblings such as search_posts or channel_stats.

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