tp_list_groups

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

No annotations provided; description states it lists groups and returns fields, but doesn't mention any behavioral traits like authorization scope or side effects. It is adequate for a read-only list.

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 sentences, front-loaded with purpose and immediate details. No redundant or extraneous text.

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 tool with no parameters and no output schema, the description adequately covers purpose and return fields. Could mention if results are paginated or sorted, but not necessary for a simple 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?

No parameters (baseline 4). Description adds context that the tool returns id, name, athlete_count, is_default, which is helpful beyond the empty schema.

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?

Description clearly states action ('List'), resource ('coach's athlete groups'), and return fields. It distinguishes from sibling tp_list_athletes_in_group by focusing on groups themselves, not athletes within.

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?

Implicit that this is for listing groups, but no explicit guidance on when to use vs alternatives like tp_list_athletes_in_group or when not to use it.

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