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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely non-structured context: the watchplus:read permission requirement and the negative-space guarantee that emails and pending invitees are never returned, which matters for privacy-sensitive answers.

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?

Dense and front-loaded: scope first, then output contents, then the follow-up tool and tie-break rule. Every sentence carries information, though "Proceed directly when the people are clear" is a slightly loose autonomy hint that could be tightened.

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, the description need not describe return fields, and rich annotations cover safety; auth and result-set exclusions are still spelled out. The one real gap against tool complexity is that result-set sizing and pagination are never mentioned despite limit/offset params.

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 reported as 0% for the nested request, so the description must compensate. It does explain the query semantically (group or member name; match usernames to disambiguate duplicates) but says nothing about limit (default 10, max 20) or offset paging, leaving pagination behavior undocumented in both places.

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?

"Find the connected viewer's accepted Watch+ groups by group or member name" names a specific verb, resource, and scope, with an example query (Jenna). It is clearly distinguishable from recommend_for_group and search_titles, though it never explicitly contrasts with get_watchplus_context, which is the nearest sibling by name.

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?

It routes the agent forward ("Use these IDs ... then recommend_for_group") and gives a concrete tie-break rule: prefer the smallest matching group when people overlap, unless the viewer names one. What is missing is an explicit when-not/alternative case, e.g. when to call get_watchplus_context instead.

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