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

Goes well beyond the annotations: discloses the required permission (manage_broadcasts), confirms no network call to Telegram is made (reinforcing the openWorldHint=false claim), and states that all catalogued operations read public data only. The mention of input schemas, permissions and limits also conveys what the response contains, which matters since no output schema 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 compact sentences, each carrying distinct information: purpose, permission prerequisite, no-connection caveat, and the botId defaulting rule. The most decision-relevant facts come first with zero 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 zero-required-parameter read-only catalog with no output schema, the definition covers what the tool returns and the one non-obvious parameter rule. Nothing an agent needs in order to call it correctly is missing.

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 coverage is only 50%, but the description compensates for the undocumented botId parameter by explaining it may be omitted when the application has exactly one userbot. applicationId is already fully specified in the schema, including the MCP_APPLICATION_REQUIRED failure mode, so both parameters end up covered.

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 verb ("Discover") and a concrete resource (supported Telegram MTProto account operations, their input schemas, permissions and limits). An agent can distinguish this catalog from execute_telegram_operation or get_telegram_operation by the "discover/catalog" framing, though no sibling is named 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?

The description establishes the prerequisite ("Requires manage_broadcasts") and the important scope caveat ("this catalog does not connect to Telegram"), which implies it is a discovery step rather than an execution step. It never explicitly says "use execute_telegram_operation to actually run one," so the when-to-use routing is left to inference.

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