telegram_get_chat_member_count

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

No annotations are provided, so the description carries the behavioral disclosure burden. It does state the return format ('Member count integer formatted as string') and implies a read-only operation, but it does not mention error cases, permissions, or behavior when chat_id is null/default. This is minimal but not completely opaque.

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 short and front-loaded with the core purpose, followed by compact param/return documentation. Each sentence contributes useful information, though the param line adds little beyond the schema field name.

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?

The tool is simple with one parameter and an output schema, so the description does not need to explain return structure in detail. However, it lacks usage guidance, sibling differentiation, and any caveats about chat_id being optional/nullable, leaving some ambiguity for an agent deciding how to invoke it correctly.

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 the schema's lack of parameter documentation. It only restates the parameter name ('Target chat identifier') without adding format details, examples, or clarifying the default null behavior. The meaning is essentially the same as the schema's 'Chat Id' title.

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 identifies the action ('Get the total number of members') and the resource ('a group, supergroup, or channel'). It does not explicitly distinguish itself from siblings like telegram_get_chat, but the purpose is specific enough for an agent to understand what it does.

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 provides no guidance on when to use this tool versus alternatives such as telegram_get_chat or telegram_get_chat_administrators. It only states the operation and parameters, leaving selection criteria entirely to inference.

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