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

The description adds context beyond the openWorldHint and destructiveHint annotations by explaining the allow_dangerous gate and stating that success returns an API result dict or normalized error. It also links to full documentation, increasing transparency though it doesn't detail error cases or side effects further.

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 three concise sentences, front-loaded with purpose, then safety, then result/links. No wasted words; every sentence earns its place and the structure is easy to scan.

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?

Given the complexity of an open-world low-level API invoke, the description covers the essential aspects: purpose, safety gate, result format, and a documentation link. With an output schema present and good annotations, it is reasonably complete, though it could briefly mention advanced usage risks or method normalization, but that is not critical.

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 covers all parameters with detailed descriptions (100% coverage), so the description adds little new parameter-level meaning. It does reinforce the allow_dangerous behavior ('Dangerous methods require allow_dangerous=true'), but this is already present in the schema, keeping the score at the baseline.

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 clearly states the tool is a low-level Telegram API (MTProto) invoke for methods not wrapped by other tools, using the specific verb 'invoke' and identifying the resource. It distinguishes itself from sibling tools by explicitly positioning itself as a fallback for unsupported methods.

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?

It provides explicit guidance: use for methods not wrapped by other tools, and requires allow_dangerous=true for dangerous methods. This gives clear context for when to use this tool versus alternatives, though it doesn't enumerate specific sibling exclusions beyond 'other tools.'

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