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

Beyond the readOnly/openWorld annotations, the description discloses cost ($0.002 USDC per successful call), the payment rails (x402 on Base, Solana or Arc), that failed calls are not charged, and the pagination ceiling (up to 100 ads per page, page 1–50). It also identifies the upstream source as SEEK's public job-search JSON service, which tells the agent about data freshness and coverage limits.

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?

Front-loaded with the resource and source, followed by a compact pricing/pagination sentence — no filler. The long enumerated field list is dense but earns its place by telling the agent what columns to expect; only slight cost to readability.

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?

With an output schema present, return-value explanation is optional, yet the description still summarizes returned fields. Cost, payment mechanism, pagination limits and data source are all covered; the only gap is routing guidance relative to the dozens of sibling job boards.

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 every parameter is already documented in structured data; the description only restates the page-size ceiling and the general keyword/place framing. It adds no semantics beyond the schema, such as how `where` interacts with `country` or what relevance sorting optimizes for, so 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 (SEEK Australia/New Zealand job ads), the query inputs (keywords + place), and enumerates the returned fields and total match count. It explicitly scopes to SEEK AU/NZ, which cleanly separates it from the many other job-board siblings such as jobs_indeed, jobs_reed_co_uk, or jobs_seekinalpha-style aggregators.

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?

Usage is implied by the source and country scope — an agent can infer this is the tool for SEEK AU/NZ searches — but there is no explicit when-to-use/when-not statement or pointer to a sibling board for other regions. No prerequisites or exclusions are stated.

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