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

The annotations already declare readOnlyHint true, idempotentHint true, and destructiveHint false, so the safety profile is covered. The description adds value by enumerating exactly what data is returned (title, company, location, workplace type, employment type, posted date, source, apply link, open status, description excerpt).

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?

Two sentences carry a high density of information: the resource scope, the full field list, and the expected input source. Everything earns its place and the critical guidance about passing the search_jobs link appears early.

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?

For a single-parameter, read-only retrieval tool, this description is complete. It names the full return contents (obviating the need for an output schema), explains how to supply the URL, and connects the tool to the search_jobs workflow.

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 100% and the schema's parameter description already states "The job link as returned by search_jobs." The tool description repeats this guidance but adds no new format, pattern, or validation details, so it stays at the baseline for fully documented parameters.

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 states a specific action and resource: it returns "full details of one posting" indexed by HuntBoard. It also differentiates from its sibling search_jobs by instructing the agent to pass a link returned by search_jobs, making the tool's role 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?

The description explicitly tells when to use this tool: after getting a link from search_jobs. It does not, however, spell out when not to use it or compare against alternatives like list_coverage, so it falls just short of a full 5.

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