get_logged_in_athlete_clubs

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly states 'Read-only operation,' which conveys safety, and implies authentication via 'authenticated athlete.' However, it does not mention pagination behavior, potential empty results, or response format, leaving some transparency gaps.

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 a clear structure: title, endpoint, description, and read-only flag. Every sentence earns its place, and there is 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?

Given the low complexity (only two optional parameters, no output schema) and the presence of a clear description of purpose and safety, the description is adequate. It omits details like response structure or error handling, but these are not essential for the agent to invoke the tool correctly.

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?

Both parameters (page, per_page) are fully described in the input schema (100% coverage), so the baseline is 3. The description adds no additional meaning about these parameters, merely relying on the schema for their semantics.

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 clearly states the tool lists clubs for the authenticated athlete, using specific verbs ('List', 'Returns a list') and a precise resource ('clubs whose membership includes the authenticated athlete'). It stands apart from sibling tools like get_club_by_id by focusing on the athlete's own memberships.

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 clear context for when to use the tool: to retrieve clubs associated with the logged-in athlete. It does not explicitly mention alternatives or exclusions, but the context is unambiguous enough for an agent to infer its appropriate use.

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