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

The annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false). The description adds meaningful context beyond them: the data is aggregated, computed directly from the database rather than estimated, and scoped to currently published listings. It does not discuss performance, rate limits, or response format, keeping it from a 5.

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 sentences, front-loaded with the resource and operation, then the enumerated aggregates. Every clause carries information, and the closing distinction ('not an estimate') is a compact, useful qualifier.

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 one-parameter read-only tool with rich annotations and a fully described input schema, the description is complete. Although no output schema exists, the enumeration of computed aggregates effectively communicates what the tool returns, leaving no critical gap for correct invocation.

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% for the single top_n parameter, so the schema already documents its range, default, and meaning. The description does not mention top_n or explain how it affects the output, so it adds no parameter-level value beyond the structured schema; baseline 3 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?

The description names a specific resource (currently published Level listings) and a precise operation (aggregated statistics), then enumerates the exact aggregates: AI level distribution, remote share, and frequent tools/categories. This cleanly separates it from siblings like search_jobs, get_job, and latest_ai_jobs, which return individual listings rather than aggregates.

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 description implies usage by framing the tool as aggregate market statistics, so an agent can infer it is for trend/overview queries rather than individual job lookup. However, it never explicitly states when to choose this over siblings such as latest_ai_jobs or search_jobs, nor does it give any prerequisites or exclusions.

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