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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false. The description's 'Read-only' merely restates readOnlyHint and adds no behavioral context such as error behavior, permissions, or pagination. It does not contradict annotations, but it adds little beyond them.

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?

Two short sentences, front-loaded with the returned resource. The second sentence ('Read-only') duplicates annotation data and is slightly wasteful, but overall it is appropriately terse.

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?

For a simple get-by-ID tool with full schema coverage, rich annotations, and an output schema, the description covers what is returned. It still leaves gaps around how the group relates to network people and when this tool is preferred over the list, person, event, or organization variants.

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?

Both required parameters (companyId and groupId) are fully documented by the schema with UUID wrapper descriptions, so the 100% schema coverage baseline is 3. The description does not explain the parameters or their roles beyond 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 description names the resource ('one chat group') and its contents ('the network people in it'), and the singular 'one' distinguishes it from list_network_groups. It omits an explicit verb, but the intent is clear from the name and title. No sibling alternative is named.

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 statement of when to use this tool versus list_network_groups or the related get_network_person, get_network_event, and get_network_organization tools. The only usage-like note is 'Read-only,' which describes safety rather than selection criteria.

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