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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered externally. The description adds no behavioral context such as auth requirements, rate limits, or whether the key is stable, and merely restates that a single posting is returned.

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?

The description is a single front-loaded sentence with no redundant wording. It is efficient, though arguably too terse given the gaps it leaves.

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?

An output schema exists, so return values need not be described. For a simple single-record lookup with readOnly and openWorld annotations, the definition is minimally adequate, but it lacks any pointer to obtaining the job key or to the search sibling.

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?

With one required parameter (jk) at 0% schema description coverage, the description does compensate partially by equating 'jk' with 'job key'. However, it gives no format details, no example, and no hint about where to obtain a valid key.

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 'Single Indeed job posting by job key' names a specific resource (job posting) and the selector (job key), so an agent can tell it apart from search-style siblings. It does not explicitly name the sibling indeed_search, but the singular retrieval framing is clear.

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 prerequisite explanation, and no alternative tool named. Usage is only weakly implied by 'by job key' — an agent must infer that it needs a key obtained from indeed_search.

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