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

With no annotations, the description carries the disclosure burden. It adds valuable behavioral context: no Telegram account/authentication needed, results are from the public catalog rather than the user's joined communities, and results include subscriber/member counts, categories, and trust scores. It stops short of disclosing rate limits, ordering, or pagination, but the core access behavior is clearly disclosed.

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?

Two dense sentences cover catalog scope, scale, result fields, access requirements, and a filter hint without filler. The main subject is front-loaded and each clause contributes information.

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 description gives enough operational detail for an agent to invoke the tool: what is searched, which entities, what filters exist, and what fields the results expose. Without an output schema, it usefully previews return content; it could also mention ordering or that results are ranked by relevance, but that is a minor omission.

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?

All three parameters are already fully described in the schema, including enum values, defaults, and bounds, so the description doesn't need to add much. The 'Use type to restrict to one entity kind' line reinforces the enum semantics but adds no new detail 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?

States a specific action ('full-text search') over a named resource (the tgden catalog) and enumerates the entity kinds and result fields. This clearly separates it from sibling stats tools such as channel_stats and from message-level search_posts, even though it doesn't name them explicitly.

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?

Gives clear context on when to call it—public catalog search that requires no Telegram account and finds communities the user has NOT joined—plus a filter directive via type. It does not explicitly name sibling alternatives or state when not to use it, so it lacks explicit exclusions.

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