channel_getClassInfo

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

No annotations are provided, so the description carries the full burden. It does not disclose any behavioral traits such as whether the operation is read-only, what the return value looks like, or any side effects. The phrase 'Get the channel' suggests a read operation but gives no useful detail.

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 extremely short, but it is under-specified rather than concise. It lacks structure and fails to provide essential context. A single vague sentence is not an effective use of brevity.

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 and no annotation support. The description does not explain what 'class info' is, what the result contains, whether chatId is optional or required, or any other context. It is incomplete for a tool that likely returns a structured data object.

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 100% of the parameters with clear descriptions and examples, so the schema is the primary source of parameter semantics. The description adds nothing beyond this, matching the baseline of 3 for high schema coverage.

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 says 'Get the channel' which is vague and does not clarify what 'class info' means. It could be interpreted as fetching channel metadata, but it doesn't distinguish this from sibling tools like client_getChatById or channel_getSubscribers. It is closer to a tautology since the tool name already implies getting channel class info.

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?

There is no guidance on when to use this tool vs alternatives. The description does not mention any prerequisites, exclusions, or specific scenarios where this should be preferred over other channel-related tools. It is entirely absent.

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