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

The annotations already declare this as a safe read operation (readOnlyHint=true). The description adds that it returns clubs where the athlete is a member, but it does not disclose pagination behavior or return format beyond 'a list'. This adds some context but misses key behavioral details.

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 a single sentence that directly states the tool's function. It is concise, front-loaded with the title, and contains no redundant or excessive wording.

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?

The tool is simple with two optional parameters and no output schema. The description covers the main purpose but omits pagination semantics and the nature of the returned list (e.g., that it contains club objects), leaving some gaps for an agent needing to invoke it 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?

The schema provides no descriptions for 'page' and 'per_page', and the tool description does not mention them at all. With 0% schema description coverage, the description fails to compensate for the missing parameter semantics, leaving the agent to infer their meaning.

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 that the tool lists clubs for the authenticated athlete, using a specific verb (List/Returns) and resource (clubs). It distinguishes itself from sibling tools like getClubById, which target specific clubs.

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 implies the tool is for retrieving the current user's club memberships and provides clear context from the resource name. However, it does not explicitly mention when to use it versus alternatives or provide exclusions, so it falls slightly short of full guidance.

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