get_my_clubs

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

The description discloses pagination behavior via parameters 'page' and 'per_page', but it does not mention that the tool is read-only, authentication requirements, or what happens with no results. Annotations are absent, so the description partially fulfills the transparency burden.

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?

The description is extremely concise with one line stating the purpose and a brief Args list. Every sentence is necessary, and there is no fluff.

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?

Given that an output schema exists, the description covers the essential operation for a simple list tool with pagination. It omits details like authentication or result ordering, but these are not critical for basic use.

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?

The input schema has 0% description coverage, but the description explains both parameters: 'Page number (default 1)' and 'Items per page (default 30)'. This adds meaning beyond the schema's type and default values.

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?

The description uses a specific verb 'List' and clearly identifies the resource 'clubs' with the scope 'the authenticated athlete is a member of'. This distinguishes it from sibling tools like 'get_club' (single club) and 'get_club_members' (list of members for a club).

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 description provides no guidance on when to use this tool versus alternatives such as 'get_club', 'get_club_activities', or 'get_club_members'. There is no explicit when-to-use or when-not-to-use information.

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