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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so safety is covered; the description adds genuinely new behavior detail by declaring exactly which related collections come back and that activities are conditional on include_activities. It does not mention pagination or response shape, but for a single-record read the remaining gap is small.

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 front-loaded sentence carries the returned fields and the conditional flag; nothing is redundant. The trailing "POST groups/detail" is a transport/endpoint detail that earns only marginal place but does hint that a body is used for the detail call.

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 carries the burden of explaining what is returned, and it does so by naming the related collections and the flag that widens the payload. Combined with annotations covering the read-only profile, an agent has enough to call this correctly.

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 50%: include_activities is already documented in the schema, and the description's restatement adds no syntax or default info beyond it. group_id has no schema description, and the description only implies "id" without clarifying the group identifier type or source; with half the parameters documented, 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?

"One group by id" states a specific verb+resource and scope, and the enumeration of included sub-resources (addresses, policies, custom fields) makes the payload concrete. It implicitly contrasts with the sibling search_groups (single record by id vs. search), but never names that alternative explicitly.

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: fetch-by-id is a standard pattern, and the include_activities flag hints at a lighter-vs-heavier call. There is no explicit statement of when to prefer this over agencybloc_search_groups or agencybloc_list_activities, and no prerequisites or error case (e.g., unknown id) are noted.

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