telegram-approve-join-request

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

The description adds the constraint that basic groups are not supported and the permission requirement, which are useful behavioral traits beyond the annotations' readOnlyHint=false and openWorldHint=true. However, it does not detail side effects, error conditions, or state changes.

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 concise: two sentences, no redundant words, and captures the core purpose and a key requirement efficiently.

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 tool's simplicity (3 params, no output schema), the description covers the main aspects: action, supported chat types, and permission needed. It lacks details on idempotency or error conditions but is largely sufficient for accurate invocation.

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 already provides full descriptions for all three parameters (100% coverage), so the description adds minimal additional semantic value, only clarifying the pending state of requests.

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 action (approve or deny a pending join request), the target resource (supergroup or channel), and a critical constraint (basic groups not supported). This distinguishes it from sibling tools like kick-user or invite-to-group.

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 mentions that admin with invite_users permission is required, which gives usage context, but it does not explicitly compare to alternatives or state when not to use this tool relative to sibling tools.

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