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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains that this is a public-catalog search rather than an account-bound Telegram query, notes that it finds unjoined communities, and implies a read-only operation. It does not cover ordering, errors, or rate limits, but this is adequate for a catalog 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?

The description is two sentences with no wasted words. It front-loads the core function and scale, then adds the important no-account caveat and the parameter guidance. Every sentence earns its place.

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 3-parameter search tool with no output schema or annotations, the description covers purpose, scope, entity types, key result fields, and the critical no-account caveat. It is missing explicit alternative routing and a few return-shape details, but an agent can invoke it correctly with the information provided.

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 has 100% description coverage, so the baseline is 3. The description only restates the type-filter concept ('Use type to restrict to one entity kind') and adds no syntax, formatting, or search-semantics detail beyond what the schema already provides.

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 names a specific action ('Full-text search') over a concrete resource ('the tgden catalog'), lists the entity kinds (channels, group chats, bots), and mentions the result dimensions (subscriber/member counts, categories, trust scores). This makes it unambiguous and clearly distinguishable from siblings like search_posts.

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 context: no Telegram account is needed, it searches the public catalog, and it finds communities the user has NOT joined. It also tells the caller to use 'type' to restrict entity kind. However, it does not explicitly name alternative tools or state when not to use this one.

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