aidoo_get_gym_statistics

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 states 'retrieves statistics' but does not clarify whether the operation is read-only, what statistics are included, how the default gym is determined, or what the response structure looks like. The schema mentions optional gym_id and default gym, but the description adds no behavioral context beyond the verb.

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 immediately conveys the core purpose. It is well-structured and front-loaded, with no wasted words. However, it is perhaps too terse to cover necessary context, but for conciseness alone it scores high.

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 presence of multiple sibling tools and the absence of annotations and output schema, the description is incomplete. It does not specify what statistics are returned, how to interpret results, or how this tool relates to similar tools like aidoo_get_member_statistics. This leaves significant gaps for an agent trying to decide when to invoke this tool.

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 description covers the single parameter (gym_id) 100%, including that it is optional and uses a default gym. The description does not add any additional parameter meaning beyond what the schema already provides, so a baseline score of 3 is appropriate.

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 ('Rufe ab' = retrieve) and clearly identifies the resource ('Statistiken für ein Studio'). It is unambiguous that this tool retrieves statistics for a gym. However, it does not explicitly differentiate from sibling tools like aidoo_get_gym or aidoo_get_member_statistics, so it lacks explicit sibling distinction.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention contexts, prerequisites, or alternatives. The description provides only a bare statement of function without any usage context.

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