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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: it explains pagination ('pass next_cursor to get the next page') and enumerates the returned record fields, which is important since there is no output schema. It stops short of noting rate limits or result-size behavior.

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, with the purpose front-loaded, then pagination, then a field enumeration. The dense field list is justified because no output schema exists, though it could be slightly tightened.

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 six-parameter statistics tool with no output schema, the description covers the return shape and pagination adequately, and annotations cover the safety profile. The main gap is the absence of any differentiation from job_ads_national, which an agent would need to select correctly.

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%, so the schema already documents all six parameters, including the dimension values and the date variants. The description largely repeats the dimension list and otherwise describes return fields rather than adding parameter meaning, so the 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 states a clear resource and granularity (open job ads, per day), so an agent knows it is a statistics query over daily job-ad data. However, it never distinguishes itself from the sibling job_ads_national, leaving the daily-vs-national split ambiguous.

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?

There is no guidance on when to use this tool versus alternatives such as job_ads_national, nor any stated exclusions or prerequisites. Usage is only implied by the presence of the dimension parameter, which is not the same as routing guidance.

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