ClassesGetStatistics

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

The read-only nature is consistent with annotations (readOnlyHint=true, destructiveHint=false), so there is no contradiction. However, the description adds no behavioral context beyond those annotations: it does not explain what kind of statistics are returned, how the optional IDs affect the result, or what the response contains.

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 only one short sentence, which is concise, but it is under-specified rather than efficiently informative. It front-loads a tautological statement and contains no additional structure or useful context.

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?

With no output schema, no required parameters, 0% schema description coverage, and no description of what constitutes 'statistics,' this is not enough for an agent to confidently invoke the tool. The read-only annotation and parameter names offer only minimal scaffolding.

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?

Schema description coverage is 0%, so the description must compensate for undocumented parameters. It does not mention bodyClassId or bodyPupilId at all, leaving the agent without any added meaning beyond the bare property names and int64 types in the schema.

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 'Get class statistics' is essentially a rephrasing of the tool name ClassesGetStatistics. It identifies a verb and resource at a high level, but 'class statistics' is undefined and the description does nothing to differentiate this tool from sibling class-related tools such as GroupClassesGetDetail or ScheduleGetPupilSchedule.

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 about when to use this tool instead of related class, pupil, schedule, or statistics tools. No prerequisites, exclusions, or alternative selection criteria are provided, so the agent must guess from the name alone.

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