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

Goes well beyond the readOnlyHint/openWorldHint annotations: it discloses that free results are truncated, that upgrades are paid via x402 with no Apify account, that a Bearer tt_ token yields full billed results, and quotes exact rate limits (3/IP/UTC day, shared ASN pool 50, 100 global). This is precisely the operational context an agent cannot get from structured fields.

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?

Purpose is front-loaded in the first sentence, and every following sentence adds operational value (result limits, auth, quotas). The payment/auth/quota clauses run together somewhat, but no sentence is wasted.

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 no output schema, the description still tells the agent what comes back (a limited free result plus paid upgrade links) and what unlocks full results. The only soft spot is that it never specifies what 'jobs platform' detection actually returns (e.g. ATS vendor name), but auth, cost, and quota are all covered.

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 coverage is 100% for the single url parameter, and the description's 'Use for one url' only restates the single-URL constraint already encoded in the schema ('One public HTTP(S) URL', additionalProperties false). Baseline 3 for full schema coverage with no added format or validation detail.

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 opening sentence gives a specific verb and resource: detect a site's public jobs platform. It is clear enough for an agent to distinguish it from generic fetch/HTML tools, though it doesn't name a sibling (e.g. find_one_job) that might be the closer alternative.

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?

Explicitly scopes usage: 'Use for one url. Not for batch work or unrestricted monitoring,' which is a real when-not statement. It stops short of naming which sibling to use for the batch case, but the boundary is stated plainly.

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