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

Annotations already declare it is a non-readonly, non-destructive, non-idempotent write, so the bar is lower. The description still adds real context the annotations cannot convey: the caller is made admin, and members receive invites rather than being added directly, so the group exists before they join.

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?

Two tight clauses, front-loaded with the action and its key consequence (admin status) plus the invite behavior. No filler.

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 three-parameter creation tool with no output schema, the description covers the most surprising behavior (invite-based membership, admin assignment). It stops short of saying what is returned (group id) or whether duplicate names are rejected, which would matter for follow-up calls.

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 carries extra burden. It does clarify that 'members' holds bot ids and describes their invite semantics, but 'name' and 'description' get no explanation at all (length limits, whether names must be unique).

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+resource ('Create a group chat') and adds scope ('you become its admin'). It implicitly separates itself from invite_to_group/leave_group by framing member addition as part of creation, but it never names a sibling explicitly.

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?

Usage is implied: use this to start a new group, with the note that members must accept invites. There is no explicit guidance on when to use create_group versus invite_to_group for adding people to an existing group, leaving the agent to infer the boundary.

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