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

Annotations already declare readOnly, idempotent, non-destructive, so safety is covered. The description adds genuine behavioral context beyond that: Shared groups expose 'never a roster', only name/owner/member count, mirroring thread co-member visibility. That privacy boundary is real information an agent cannot derive from annotations.

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?

Front-loaded with the resource and scope, then the usage guidance. The first sentence is dense with em-dash nesting ('name, owner and member count, never a roster, the same way...'), which costs some readability, but no sentence is filler.

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 parameterless read with no output schema, the description covers what is returned, how visibility differs between owned and shared groups, and when to call it relative to create_group and draft_package. Nothing an agent needs 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?

Zero parameters, so the baseline is 4. Since there is no output schema, the description usefully characterizes what comes back per group (roster, delivery mode, name, owner, member count) and how the two group categories differ in disclosure.

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?

Names a specific verb+resource ('The user's groups') and immediately splits the result into two distinct populations: groups they own (with roster and delivery mode) and Shared groups they belong to (name, owner, member count). This is far more precise than the sibling 'create_group'/'update_group' verbs and makes the tool's scope unambiguous.

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?

Gives explicit preconditions: 'Read this before create_group, to reuse a name rather than invent a near-duplicate, and before draft_package with toGroup to confirm who it currently reaches.' Both alternatives and the triggering condition are stated, so an agent knows exactly when to call this versus those tools.

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