get_group

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description's addition of "(admin only)" is genuine context beyond annotations, but it does not mention authorization failure modes, whether missing groups error out, or any depth/pagination behavior for the included users and memberships.

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 short sentence with no filler; the result contents are front-loaded. It is efficient but reads as a fragment rather than a statement of action, which slightly weakens front-loading of the verb.

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, the description usefully names what comes back (users and project memberships), which is real value for an agent planning a call. However, a 1-parameter tool at 0% schema coverage still leaves the id's meaning ambiguous, and nothing describes failure or permission-denied behavior.

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% for the single required group_id parameter, so the description must compensate and it does not — it never clarifies that the id is the numeric group identifier or where such an id comes from (e.g., list_projects output). One bare undocumented parameter places this below the 3 baseline for fully covered schemas.

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 phrase "A group with its users and project memberships" conveys the resource and the shape of the result, which distinguishes it from list_projects or list_users. But it is a noun fragment with no verb, so the retrieval action is only implied by the name get_group rather than stated; an agent must infer that it fetches a single group.

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 only guidance is the parenthetical "(admin only)", which is a permission prerequisite rather than a when-to-use rule. Nothing says when to call get_group versus get_project, list_project_members, or list_users, and there is no mention of behavior when the group is absent.

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