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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds real value beyond that by disclosing ordering ('newest first') and that each row carries the per-client result, which is meaningful for a tool with no output schema. It stops short of describing pagination or what a truncated/empty result looks like.

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?

One front-loaded sentence naming the resource and ordering, followed by a single actionable follow-up pointer. No filler, nothing buried.

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 read-only tool with no output schema, it covers purpose, ordering, and payload shape, but leaves two undocumented optional parameters and their default behavior (all groups? default limit?) unexplained. An agent can call it, but not confidently control scope or result size.

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 0% and neither parameter is explained: it's unclear whether groupId narrows to one group and what happens when omitted (it is not required), or how 'limit' interacts with the newest-first ordering. The only ID mentioned (assignmentId) isn't even a parameter of this tool, so the description does not compensate for the coverage gap.

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?

States a concrete verb+resource (listing what the coach has given to groups) and enumerates the assignment types covered — workouts, nutrition plans, habits, messages, check-ins, sessions — plus ordering. It is clearly distinguishable from write siblings like assign_workout_to_groups or undo_group_assignment, though it doesn't explicitly contrast with read siblings like list_groups_for_client or get_group_overview.

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 only usage guidance is the follow-up step: 'Use an assignmentId with undo_group_assignment', which tells the agent where the IDs lead but not when to call this vs. get_group_overview or list_groups_for_client. When-to-use is only implied by the resource description.

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