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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that the returned data is a curated held record (activities, industries, location, open-posting count), which is modest added context for a read tool whose output schema carries the return contract.

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?

One sentence, front-loaded with the action and resource, then the returned content. No filler, though the colon-list makes it slightly run-on where two shorter sentences would read cleaner.

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 tool with an output schema and full annotation coverage, the definition gives what an agent needs: what it fetches, the key it needs, and the shape of the payload. Only the sibling routing and invalid-slug behavior are unaddressed.

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 single parameter is already documented in the schema as an identifier carried by a result's company_slug. The description restates that same meaning without adding format, casing, or validation detail, so the baseline of 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?

Specific verb-and-resource pair ('Read ... one employer') with the lookup key named explicitly ('by the slug a result carries') and the payload enumerated. It implicitly separates itself from search_companies by emphasizing a single employer, but it never names the sibling tools outright.

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?

'By the slug a result carries' implies the precondition that a slug must come from a prior search result, which is useful implied guidance. There is, however, no explicit when-to-use versus search_companies or get_job, and no stated failure behavior for an invalid slug.

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