group_metadata

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

No annotations are provided, so the description carries the full burden. It says 'Check' which implies a read-only operation, but it does not disclose whether this is safe/idempotent, whether it requires authentication, or what happens if the group doesn't exist. For a tool with no annotations, this is a notable gap.

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 a single short sentence that front-loads the action and lists the covered aspects. It is efficient and easy to parse, though it could be slightly more explicit about usage context.

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?

With no annotations and no output schema, the description must explain behavior and return value expectations. It lists what is checked but not what the response looks like, whether it can fail, or any side effects. For a simple read tool this is borderline adequate, but the lack of any behavioral detail makes it incomplete.

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 coverage is 100% and the single parameter 'jid' is described with an example format. The description adds the context that the jid refers to a group and that the tool returns metadata about it, but it doesn't add much beyond the schema. Baseline 3 is appropriate.

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 states a specific verb ('Check') and resource ('one group'), and enumerates the aspects it covers: subject, participants, admins, timestamps. This is clear enough to distinguish it from sibling tools like group_list_live or group_leave, though it doesn't explicitly name a sibling alternative.

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 implies usage: call this when you need metadata about a single group. It does not explicitly state when not to use it or mention alternatives like group_list_live for listing groups, but the scope is reasonably clear from the wording.

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