Get full channel/supergroup info

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

Annotations already declare readOnlyHint=true (safe read) and openWorldHint=true. The description adds transparency by listing the specific info fields returned (about, participants count, linked chat, slow mode), which is useful context beyond the annotations. It does not mention any side effects, consistent with a read-only operation.

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 a single, front-loaded sentence that directly states the purpose and examples. Every word is useful, with no redundancy or wasted content.

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?

There is no output schema, so the description carries the burden of informing the agent about the return value. It lists some returned fields but does not exhaustively describe the output shape or the purpose of 'accountId'. For a simple read-only info tool, the description is adequate but incomplete.

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 description coverage is 0%, so the description must compensate for parameter documentation. It implicitly explains the 'channel' parameter by referencing 'a channel or supergroup', but the 'accountId' parameter is not mentioned at all, leaving a gap. The description only partially compensates for the missing schema descriptions.

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's function: 'Return extended info for a channel or supergroup', with specific examples of the information returned (about, participants count, linked chat, slow mode). This distinguishes it from sibling tools like 'get_user_info' (for users) and other channel mutation tools.

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 implies usage when channel/supergroup extended info is needed but does not explicitly state when to use it versus alternatives. No exclusionary or alternative guidance is provided, making the usage context 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.