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

Beyond the readOnlyHint annotation, the description discloses substantial runtime behavior: the manage_broadcasts permission requirement, one-hour result expiry, 60-second timed_out semantics, offline/restarted-runtime implications, and throttling retry rules. This gives the agent the full lifecycle picture of an async operation. There is no contradiction with the annotations (readOnlyHint=true is consistent with 'Read').

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?

Five tightly packed sentences, each earning its place: purpose, permission, polling cadence, expiry, timeout behavior, and retry handling. No filler or repetition of schema content, and the core purpose is front-loaded.

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?

Despite having no output schema, the description covers the essential operational envelope: what it reads, how to poll, result expiration, timeout meaning, and error retry handling. It references key result fields (timed_out, error.retryAfterSeconds). The only gap is that the full return shape is never described, which matters more because no output schema exists.

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 33% (only applicationId is documented), so the description must compensate. It does address the highest-risk semantic: requestId, botId, and applicationId must be the same ones used at submission, and it references requestId as the operation identifier. However, botId's format and purpose remain under-specified beyond the matching constraint, so compensation is strong but not complete.

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 a specific verb and resource: 'Read a Telegram operation status and result' — clearly a read/scoping action distinct from create/list siblings. It names the identifying key (requestId) and scoping constraint (same applicationId/botId as submission), so an agent can distinguish it from execute_telegram_operation (submission) and list_telegram_operations (bulk query) without opening their schemas.

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 strong operational context: poll every two seconds, results expire after one hour, timed_out means no result within 60 seconds and a new request is needed, and throttling errors require honoring error.retryAfterSeconds. This effectively documents the polling workflow around execute_telegram_operation. However, it never explicitly names an alternative tool or states a when-not-to-use condition, leaving the sibling differentiation implicit rather than explicit.

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