Group

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds two genuine behavioral facts beyond the schema: tracks are paged and members are returned owner-first. It says nothing about auth requirements or how pagination interacts with part.

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?

It is short and front-loads the resource, with no wasted words, but the telegraphic fragment style makes it cryptic rather than efficient; a single well-formed sentence would carry more at the same length.

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 output schema and a branching part enum producing three different response shapes, the description should say more about what each part returns and that page/count apply only to the tracks part. As written an agent can guess the branch but not the payload.

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 50%, so the description must carry weight. It does map the part enum values to their content ('info' = metadata and own permissions, 'tracks' = paged, 'members' = owner first), which is real added meaning, but page/count/group_id semantics are left entirely to the schema.

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 fragment 'A group: info..., tracks..., members...' names the resource and its sub-parts, and the name get_group supplies the verb. But it never states plainly that it retrieves a single group's details, nor does it distinguish itself from siblings like list_groups or get_user.

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 use this versus list_groups (listing many) or get_user, and no prerequisites or exclusions are mentioned. The only implicit cue is the part enum in the schema.

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