aidoo_get_member_statistics

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

There are no annotations, so the description must fully disclose behavioral traits. It only states the action and examples but does not mention whether the operation is read-only, whether it returns aggregated data, requires specific permissions, or how it handles invalid member IDs. This is a significant transparency gap.

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, concise sentence that front-loads the verb and resource, with no unnecessary words or repetition. It is appropriately sized for a simple tool.

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 description gives a basic idea of what the tool returns (visits, courses, etc.) but is vague about the full scope of statistics. With no output schema and no annotations, the description should more clearly specify the response content and edge cases, making it adequate but with gaps.

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 already documents member_id with a description (Mitglieds-ID), and schema coverage is 100%. The tool description adds no parameter-specific details, so the baseline score of 3 applies.

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 a specific action ('Rufe ... ab' = retrieve) and a specific resource ('Statistiken für ein Mitglied' = member statistics), with examples (visits, courses). This distinguishes it from sibling tools like aidoo_get_member (member details) and aidoo_get_gym_statistics (gym-level stats).

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?

No guidance is provided on when to use this tool versus alternatives such as aidoo_get_member_bookings or aidoo_get_gym_statistics. The description lacks selection criteria, prerequisites, or exclusions, leaving the agent without context for tool choice.

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