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

Annotations already declare readOnly/idempotent/non-destructive, so the 'Never submits an application' line is partly redundant reassurance. The added value is the data-semantics disclosure that compensation text is authoritative while absent numeric pay/units are unknown, which prevents the agent from hallucinating salary figures.

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?

Three short sentences, front-loaded with the purpose, then parameter sourcing, then the two caveats. No filler; each clause carries information.

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?

There is no output schema, yet the description sketches the return contents and flags the compensation caveat, covering the highest-risk ambiguity. Only minor gaps remain (e.g., behavior when a slug is stale or unpublished).

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%, so the description must carry the parameter burden. It adds provenance ('slugs from search_jobs') but not format or case rules, which the schema handles via regex pattern. Adequate but not compensating fully 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 description states a specific verb and resource ('Read one current published opening in full') and enumerates what the result includes (company profile, application URL, rolefig page), which separates it from list/search siblings like search_jobs and list_company_openings. An agent can tell what this tool returns without opening the schema.

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?

It tells the agent where the required identifiers come from ('Use the company and job slugs from search_jobs'), which is real routing guidance. It stops short of naming when to prefer this over check_job_posting or list_company_openings, so no explicit exclusions.

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