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 only that the payload is the stored profile fields ('what they do, which industries..., how many postings'), which is largely restated by the output schema; no permissions, staleness, or caching behavior is disclosed.

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?

A single well-formed sentence with the action and the lookup key front-loaded, and no filler. The trailing enumeration of returned fields is mildly redundant given the output schema, which keeps it from a 5.

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 one required parameter, full schema coverage, an output schema, and annotations covering the safety profile, the description supplies everything needed to invoke correctly. The only shortfall is the absence of sibling routing for an agent choosing between search_companies and this tool.

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, so the schema already explains that slug is the employer identifier matching a result's company_slug. The description reinforces provenance ('as the slug a result carries') but adds no syntax or format detail beyond the schema, so baseline 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?

States a specific verb and resource ('Read what freehire holds about one employer') and enumerates the resource's attributes, so the agent knows this is a single-employer lookup rather than a list. It does not name any sibling explicitly (search_companies, get_job), so differentiation is inferential rather than stated.

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 this tool is used to expand a company that appeared in a prior search result, which is genuine usage context. However, there is no explicit when-to-use/when-not statement and no named alternative, so the guidance remains implied.

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