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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description's contribution is the admin-only requirement, which is genuinely useful failure-mode context. However, it does not say what happens when the caller is not admin (error vs. empty result) or whether the returned URL is permanent or revocable.

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?

A single front-loaded sentence with the action first and the constraint in parentheses — no waste. It is efficient, though the terseness contributes to the parameter ambiguity noted above.

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 one-parameter read tool with annotations covering safety and no output schema, the definition covers purpose and the admin gate. What is missing is the chat_id format and the non-admin failure behavior — small but real gaps an agent would hit on first 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?

Schema description coverage is 0% — the single parameter chat_id has no description at all. The phrase "for a group" weakly implies chat_id identifies the target group, but the description never states the expected format (numeric ID, username, string encoding). With one undocumented required parameter, the description does not compensate for the schema gap.

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?

States a specific verb and resource: "Get the invite URL for a group." It is clearly distinct from the surrounding siblings (chat_settings_get, get_profile, search_chats), none of which deal with invite links. It does not explicitly contrast with a sibling, which keeps it at 4 rather than 5.

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 parenthetical "only works if operator is admin" gives a concrete precondition for calling the tool, which is more than most definitions offer. It does not name an alternative path for non-admin callers or say what to do instead, so it falls short of explicit when/when-not guidance.

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