get_classes

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

There are no annotations, so the description carries the behavioral disclosure burden. It does not mention authentication requirements, data scope beyond 'school,' pagination, return shape, or whether the operation is strictly read-only. The verb 'get' implies a read, but the description adds no meaningful behavioral context.

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 front-loaded sentence with no filler or repetition. It is concise and easy to parse; the trade-off is the lack of substance, but that is penalized in the other dimensions.

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 that there is no output schema and no annotations, this one-sentence description leaves important context undeclared: the subdomain parameter is undocumented, and no usage guidance is provided. An agent can guess that it lists classes, but cannot confidently determine how the subdomain parameter should be used or when this tool is the correct choice.

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?

There is one parameter, subdomain, with no schema description (0% coverage). The description does not mention it at all, so the agent receives no explanation of what subdomain means, whether it is required, or how it relates to 'the school.'

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 and resource: 'Get all classes in the school.' This is enough to distinguish it from siblings like get_students or get_classrooms, though it does not explicitly disambiguate 'classes' from timetable-related concepts such as get_periods or get_subjects.

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 given about when to call this tool versus get_periods, get_subjects, or get_timetable, and no alternatives or exclusions are mentioned. The only inference is that the agent should use it when it wants 'all classes,' which is minimal and indirect.

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