bale_get_group_info

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

With no annotations, the description carries the burden; 'Retrieve' implies a read-only, non-destructive operation and it enumerates the categories of data returned, which is useful. It stops short of stating auth/session requirements or any rate/visibility limits, but a return output schema exists so return values need not be elaborated.

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 no redundant clauses; every listed item (settings, member count, permissions) adds discriminating information.

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?

An output schema is present so return values are covered, and the read intent is clear, but the one required parameter is undocumented and there is no usage context, leaving modest gaps for an agent to call it confidently.

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% and the sole parameter group_id has no description anywhere. The description mentions 'group or channel' but never clarifies that group_id is the identifier for either entity or its expected format, so it does little to compensate.

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 ('Retrieve') and resource ('group or channel') plus what is returned: full information, settings, member count, permissions. This implicitly separates it from the sibling bale_get_group_members, though no sibling is named 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?

There is no guidance on when to call this versus alternatives like bale_get_dialogs, bale_get_group_members, or bale_get_user_info, and no prerequisites or session/auth context are mentioned.

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