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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds what the payload actually contains (employer record, page, open positions) and its serialization as schema.org JSON-LD. That is meaningful behavioral context beyond the annotations, though pagination or failure behavior remains unstated.

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 short sentences with zero padding; the payload scope is front-loaded and the parameter-provenance hint follows. Every clause earns its place.

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 correctly takes on the job of describing return contents and format, which it does well for a simple single-parameter lookup. It stops short of covering large-result handling (e.g., whether all open positions are returned in one payload).

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 single parameter carries no inline documentation. The description partially compensates by identifying employer_slug as coming from search_jobs, but adds no format, casing, or validation detail.

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 names a specific verb and resource ('Everything about one employer') and enumerates the returned scope: the employer, its page, and all open positions. It implicitly distinguishes itself from get_job by being employer-centric, though it never explicitly contrasts with that sibling.

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?

'Use employer_slug from search_jobs' establishes a clear prerequisite workflow (find slug via search, then fetch), which is real usage guidance. However, there is no instruction about when to prefer get_job instead, or what to do if the slug is unknown.

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