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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real value by disclosing the breadth of the returned aggregate — six distinct content areas including history and the open next action — which is not derivable from any structured field given there is no output schema.

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 compact sentence with the key fact ('one posting') front-loaded and no filler. It is telegraphic rather than grammatically complete, but every phrase maps to returned content.

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's enumeration is the only clue to return contents, and it covers the main sections. It stops short of saying how those sections are shaped (nested objects, arrays), whether missing sections appear as null, or how errors surface for an unknown posting_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?

There is a single required parameter with 100% schema description coverage and an example value ('JP-0001'). The description adds nothing about the identifier beyond the schema, so the 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 identifies the resource ('one posting') and enumerates the sub-resources returned (facts, evaluation, application, interviews, touch history, next action), which distinguishes it from single-facet siblings like hunt_contacts or hunt_due. No explicit verb, but the read intent is unambiguous.

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 only implied: an agent can infer this is the per-posting detail fetch rather than a list tool such as hunt_pipeline. There is no statement of when to prefer it over a sibling, no exclusion, and no mention of behavior when the posting_id is unknown or not found.

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