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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. Critically, there is no output schema, so the field enumeration (day, times, months, levels, subjects, teachers, seats, trial rules) is the only disclosure of what comes back — and it delivers that. Error behavior for an unknown id is not covered.

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?

One sentence, front-loaded with the scope ('One class in full') and then the payload. Every element of the list corresponds to real returned data; nothing is padding.

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?

For a read-only single-record fetch with no output schema, the return content is described well enough to decide whether to call it. Minor gaps remain around whether soft-deleted or archived classes are returned and what happens with a stale id, which are not addressed.

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 a single required parameter whose schema description ('The class's id') gives 100% coverage. The prose adds nothing about how to obtain that id or what format it takes, so the baseline 3 for a fully documented single param 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?

States it retrieves a single class 'in full' and enumerates the contained data (day, times, months, levels, subjects, teachers, seats, trial rules), which clearly separates it from list_classes and class_history. The verb is implicit rather than stated, but the resource and detail level are unmistakable.

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?

'One class in full' implies this is the detail-fetch to use after a list call, but the description never says when to use it over class_history or list_class_lessons, nor does it state any prerequisite such as needing a class id from a prior listing. Usage is inferable but not spelled out.

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