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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered without help from the description. With no output schema, the description does real work by disclosing the shape and breadth of the return payload (identity, locations, job counts by kind, pay, best-paid jobs, links). It omits what happens on an unknown slug and whether results are paginated or live-updating beyond 'right now'.

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?

It is a single front-loaded sentence that opens with the key scoping fact ('One employer') and never wastes words on throat-clearing. The enumerated payload list is long enough to read as a run-on, which keeps it off a 5, but every clause conveys distinct return 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?

For a one-parameter read tool with no output schema, the description covers the return contents in detail and the annotations cover the safety profile, so an agent has enough to invoke it correctly. The remaining gap is error behavior for an invalid or ambiguous employer name, which the description does not address.

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 parameter with 100% schema description coverage, including slug examples and a pointer to list_healthcare_employers, so the baseline is 3. The description's parenthetical '(or AI-training program or job board)' broadens what the parameter accepts, which is genuinely useful, but it largely restates acceptance criteria the schema already gives.

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 resource ('one employer... or AI-training program or job board') and then enumerates exactly what the response contains: identity, hiring locations, open jobs by kind, posted pay, newest and best-paid jobs, and links. This clearly separates it from list-style siblings like list_healthcare_employers or search_healthcare_jobs. It stops short of naming any sibling explicitly, so it's a clear 4 rather than a 5.

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: it's the single-entity detail lookup, so an agent can infer it should be called after resolving an employer via list_healthcare_employers — but that pointer lives in the schema, not the description. There is no explicit when-to-use/when-not or naming of alternatives in the description text itself. Adequate but with a clear gap.

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