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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered without the description's help. The description contributes the scope of the response (schedule, capacity, fees, registration settings), which is useful but modest added context; it says nothing about error behavior for missing ids or rate limits.

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?

Two short sentences, front-loaded with the payload summary before the endpoint path. The raw 'GET /v1/Classes/{id}' line is mildly redundant with the name and title, but it is not wasteful or padded.

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 simple single-resource read with full schema coverage and no output schema, the description adequately signals what comes back by naming the four payload areas. Nothing an agent needs in order to invoke it correctly is missing, though a note on missing-id behavior would have rounded it out.

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 coverage is 100% and the single class_id parameter is documented as a positive Jackrabbit class id with bounds, so the schema does the work. The description only restates 'by id' without adding format, source, or lookup guidance, matching the baseline for fully-covered schemas.

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 names a specific verb and resource ('One class by id') and enumerates the returned payload ('full schedule, capacity, fees and registration settings'), which clearly separates it from the listing sibling jackrabbit_list_classes and from jackrabbit_get_class_roster. It stops short of naming any sibling explicitly, so it is clear but not maximally differentiated.

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?

Usage is only implied: fetch one class when you have its id, versus listing when you don't. There is no explicit when-to-use statement, no prerequisite or permission note, and no reference to alternatives such as jackrabbit_list_classes or jackrabbit_get_class_roster.

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