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

Annotations already cover readOnlyHint, destructiveHint and openWorldHint, so repeating 'Read-only' adds little. However, the description contributes real context beyond the annotations: the untrusted-customer-content warning for message/notes text (a prompt-injection hint) and the 'Returns one page unless stated otherwise' pagination note.

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?

Four short, front-loaded sentences with no filler; the record scope and endpoint come first, then the safety and pagination notes. 'Read-only' slightly duplicates the annotations, but the rest earns its space.

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 does name the fields returned (names, membership counts, notes) and states the single-page behavior, which is what an agent needs to consume the result. Missing only error/not-found behavior and confirmation that group_id must belong to dashboard_id.

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 schema documents only that both IDs are positive integers. The path template 'GET /dashboards/{dashboard_id}/groups/{group_id}' maps each parameter to its scoping role, which is genuine added meaning, but nothing explains constraints such as whether dashboard_id must be the group's owning dashboard or what happens on a mismatch.

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 gives a specific verb and resource ('Read one record of contact group names, membership counts and notes') plus the raw endpoint, so an agent immediately knows this is a single-record fetch. The word 'one' implicitly contrasts with textrequest_list_groups, though the sibling is never named directly.

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 only implied: because both dashboard_id and group_id are required, the tool is for fetching a known group, not discovering one. There is no explicit 'use this when / not when' statement or pointer to textrequest_list_groups for enumeration, so the agent must infer the routing.

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