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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing the per-call price ($0.002 USDC via x402 across Base, Solana, or Arc), that failed calls are free, and that only ~15 postings exist per page. Payment/authorization mechanics and pagination limits are exactly the operational context an agent needs before committing to a paid call.

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, scope, and page size are front-loaded in the first two sentences, and the pricing sentence earns its place for cost-aware agents. The enumerated return fields (title, company, location type, salary, link) are somewhat redundant given an output schema exists, making it slightly longer than necessary.

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 covering return values and annotations covering the safety profile, the description supplies everything else that matters: source domain, geography, data provenance, page-size ceiling, and cost/failure semantics. Nothing an agent needs to decide and call correctly is missing.

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% and the single `limit` parameter is fully described in-schema (1 to 15, default 10). The description only adds the corroborating fact that the page holds about 15 postings, which explains the cap but adds nothing on syntax or behavior. 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?

States a specific resource (tech job postings), an explicit source (Djinni.co's public job list), and a scope (mostly Ukraine and remote roles), plus the underlying data source (schema.org JobPosting). An agent can distinguish this from the dozens of other job-board siblings by the named domain alone.

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 domain and geography imply when this board is appropriate, but there is no explicit when-to-use/when-not or comparison to any sibling such as jobs_djinni-like regional boards or jobs_multi_job_board. Usage selection is left to inference from the source name.

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