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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, and the description is consistent with them by showing a GET endpoint. It adds the returned field list, but does not elaborate on pagination behavior, auth needs, or rate limits beyond what the schema already implies.

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 with the operation and returned fields front-loaded, plus the endpoint path. There is no filler or repetition.

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 read-only list endpoint, the description covers purpose, returned fields, and the underlying API path; annotations cover the safety profile and the schema documents pagination. It could mention the pagination response shape more explicitly, but no critical information is missing.

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 both page and page_size are described directly in the schema, including the use of next_page. The tool description does not add parameter-specific semantics, so baseline 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 gives a specific verb and resource ('List labor classes') plus the returned fields (identifier, name, active flag), making the operation unmistakable. Against a large set of sibling list_* tools, the resource name alone distinguishes it cleanly.

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?

The listing intent is implied by 'List labor classes', and the tool is resource-specific enough that selection is fairly obvious. However, it does not explicitly say when to use it versus related tools like exaktime_query_odata or any get_* variant, nor does it state exclusions or prerequisites.

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