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

Beyond the readOnlyHint annotation, the description adds meaningful behavioral details: it requires manage_broadcasts, operates only on public data, and does not connect to Telegram. It also clarifies botId fallback behavior. No contradiction with annotations exists.

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 dense sentences each add value: what the tool returns, the required permission and safety profile, and an important optional-parameter rule. There is no redundancy or filler.

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 read-only catalog tool with no output schema, the description is complete: it states the purpose, return contents, permission requirement, side-effect-free behavior, and parameter caveat. An agent has enough information to invoke it correctly and interpret its role among the sibling tools.

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 schema only documents applicationId, leaving botId entirely undocumented. The description compensates by explaining botId may be omitted when the application has exactly one userbot, which adds real behavioral 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?

The description states a specific action (Discover) and resource (supported Telegram MTProto account operations), and names the kind of information returned (input schemas, permissions, limits). It clearly distinguishes this listing tool from execution tools like execute_telegram_operation.

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 provides useful context such as requiring manage_broadcasts and noting that the catalog does not connect to Telegram, which implies it is a safe discovery step. However, it does not explicitly say when to use this tool instead of get_telegram_operation or execute_telegram_operation, or mention any exclusions.

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