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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds the underlying endpoint (GET /v1/Common/JobCodes) and enumerates the returned fields, which is modest but real added context; it says nothing about pagination limits, ordering, or whether results include inactive codes by default.

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 tight sentences with the core purpose front-loaded and no wasted prose. The raw endpoint path is mildly technical filler for an agent but does add traceability, so it just misses a 5.

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 tool with no output schema, the description compensates by naming the returned fields (name, description, active flag), and annotations plus a fully documented schema cover safety and paging. The main remaining gap is the unresolved overlap with exaktime_list_jobs.

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 100%, with page and page_size fully documented (ranges, defaults, and the 'pass the previous reply's next_page' guidance). The description adds nothing about parameters, which is acceptable given the schema does all the work, but it means no credit above baseline.

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 a specific verb and resource ('List job codes') and clarifies the domain term by equating job codes with positions/trades, which helps an agent that might not know ExakTime terminology. It does not, however, distinguish this from the sibling exaktime_list_jobs, so the job-code-vs-job boundary is left implicit.

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 when-to-use or when-not-to-use guidance is given, and no alternative is named even though exaktime_list_jobs, exaktime_list_cost_codes, and exaktime_query_odata are plausible routes to overlapping data. The agent must infer applicability purely from the name.

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