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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety burden is covered. The description adds real value by defining the result set (every group owned by the authenticated user) and the domain term, but says nothing about ordering, pagination, or result shape.

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 lines with zero filler: the action first, then the definition and scope of what comes back. Every sentence earns its place.

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 no-parameter, annotation-covered list tool with no output schema, the description supplies what an agent needs to choose and call it. Only pagination or ordering behavior is unaddressed, a minor gap for a small owned-collection list.

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 there is nothing for the description to disambiguate; baseline 4 applies. The scope sentence usefully confirms the implicit filter is the authenticated user rather than any request input.

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?

Specific verb+resource ("List content groups") plus a clarifying gloss that a content group is an "app" — one per brand/project — scoped to the authenticated user. It implicitly contrasts "every" group against the singular getContentGroup sibling, but never names it or any other sibling 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?

No statement of when to use this rather than getContentGroup, updateContentGroup, listAccounts, or getGroupAnalytics. The only routing signal is the scope phrase "owned by the authenticated user," which is context rather than guidance.

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