telegram_get_chat_member_count

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

Annotations already provide strong safety profile (readOnlyHint=true, destructiveHint=false, idempotentHint=true). Description adds return format (JSON with member_count), which is useful behavioral info. No contradictions.

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?

Extremely concise: two sentences plus args/returns. Front-loaded with purpose. No unnecessary words.

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?

For a simple read operation with good annotations, the description is fairly complete. It explains what it does and returns. Could mention permissions (e.g., bot must be member), but not essential.

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%, meaning tool description adds no value beyond the schema. It merely repeats 'chat_id or @username' already present in the input schema. Does not compensate for low 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?

Description clearly states the tool gets the total number of members in a chat/channel/group, using precise verb and resource. This distinguishes it from sibling tools like telegram_get_chat_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?

No explicit guidance on when to use this tool vs alternatives. The name is self-explanatory but lacks context or exclusions.

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