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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description contributes only the word 'live' (data freshness) and 'structured', adding marginal context but nothing about missing-id behavior or scope.

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?

A single short sentence with no filler and no buried lede, which is structurally sound. The problem is under-specification rather than verbosity, so it reads as sparse rather than efficiently concise.

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?

This is a low-complexity, single-parameter tool with no output schema, so the description carries the burden of explaining the record's shape, fetch semantics, and failure mode for a nonexistent id. 'Structured record' is too vague to tell an agent what it will receive or how to recover from a bad id.

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 0%: the required integer parameter 'id' (minimum 1) is documented nowhere in the schema, and the description never mentions a parameter at all. It does not say the id is a listing/job identifier or what happens for an unknown id, so it fails to compensate for the coverage gap.

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 phrase 'One live listing as a structured record' conveys that a single listing is retrieved, which is more than the title alone. However it has no explicit verb, names no resource type (job? listing?), and gives no differentiation from the sibling tools fetch, search, or search_jobs. The purpose is only broadly inferable.

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 when-to-use guidance, no statement of prerequisites, and no routing against alternatives. An agent cannot tell from this text whether to call get_job, fetch, or search_jobs for a given need. Score 2 rather than 1 only because nothing stated is actually wrong or misleading.

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