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

With no annotations, the description carries the full burden and does reasonably well: it discloses auth requirements and a rate limit (300 calls/day) and data provenance/quality caveats ('Compiled by an AI from public careers boards, not human-reviewed; removal on request'). It stops short of describing error handling or what an out-of-range day returns.

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 compact sentences, with the core output description front-loaded and the key/rate-limit and provenance caveats following. No wasted words.

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?

No output schema, yet the description conveys what comes back (company list with change size, sorted descending) and covers auth and provenance. Remaining gaps are minor — error behavior and result format details are unspecified.

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 both parameters are already documented in the schema (day format, series start, min_delta default). The description's 'largest change first' hints at ordering relative to min_delta but adds no syntax or format detail beyond the schema. Baseline 3 is correct.

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 — companies whose open-job count changed on a given day — plus scope (a given day), direction (hiring more or cutting roles), and ordering (largest change first). It is clearly distinguishable from siblings like get_company_open_roles (single-company detail) and coverage.

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?

It gives a concrete prerequisite ('Needs a free API key (300 calls a day)') and implies a day-based lookup, but never states when to prefer this over siblings such as get_company_open_roles or coverage, nor any when-not conditions. Usage is implied rather than explicit.

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