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

Annotations already carry readOnly, idempotent, non-destructive and closed-world, so what the description adds is the important field-visibility rule: admins receive pending_requests, reported_posts and membership questions, while others see these as 0/empty. That is real behavior beyond structured metadata, though it doesn't discuss auth requirements or error cases for a nonexistent group.

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?

The first sentence front-loads the field inventory and the admin-vs-non-admin caveat comes last, which is the right order. There is mild redundancy in restating the field list twice ('name, About text, privacy, price, counts…' then 'name, the About text, whether it is private, the price…'), but every sentence still carries useful content.

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 must carry return-shape information, and it does — enumerating the fields returned plus the conditional admin-only fields. It stops short of describing the container structure or what happens for an invalid group slug, so it is strong but not exhaustive for a read tool.

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?

There is a single parameter with 100% schema description coverage ('Group URL name, e.g. yourgroup for skool.com/yourgroup'), so the schema already covers the semantics fully. The description adds no format or slug-resolution detail, which fits the baseline-3 case for well-annotated single parameters.

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 a specific resource ('A group's name, About text, privacy, price, counts, owner and membership questions') and clarifies it returns exactly one group as its About page/Settings show it, which implicitly separates it from list_groups and get_group_stats. It never names a sibling tool or explicitly states the single-vs-list distinction, keeping it just under a 5.

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 tool is contextually intelligible — fetch a single group's profile/settings — but the description contains no 'use this when' phrasing and does not mention alternatives such as list_groups, search_group or get_group_stats. Usage must be inferred from the resource name and the returned fields.

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