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

Annotations already establish readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds context the annotations cannot: channels may belong to several groups or none, groups never cross workspace boundaries, and posting via group_ids only hits ACTIVE channels. That last detail is a real behavioral caveat an agent would otherwise get wrong.

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 tight sentences with no filler, and each clause carries information (membership rules, workspace isolation, downstream use). The one structural weakness is that it leads with a definition of the object rather than with what the call does, so the agent reads a glossary entry before learning the action.

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 an output schema present, return shape need not be explained, and the description covers the semantics an agent actually needs: intra-workspace scope, multi-membership, and ACTIVE-only posting. For a one-parameter read tool this is close to sufficient; only an explicit statement of what the call returns is missing.

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 and the schema documents it fully (100% coverage, "Workspace id from list_workspaces"), so the schema is doing all the work. The description says "Groups of one workspace" but adds nothing about the parameter itself — no format, no source, no scoping caveat beyond what the schema states. Baseline 3 for high schema coverage.

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 defines the resource precisely ("named sets of its channels", scoped to one workspace) but never states the tool's own action — it never says it returns/lists the groups of a workspace. The verb lives only in the name and title, so an agent must infer that this is a read-list call rather than, say, a lookup of group metadata. Useful conceptual framing, but the purpose statement itself is implied rather than asserted.

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 closing clause routes the agent forward — "Target a group in create_post with group_ids" — which is a genuine usage hint about what the output is for. However, there is no guidance on when to choose this over list_channels or get_structure, and no statement of the prerequisite that workspace_id must come from list_workspaces (that lives only in the schema).

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