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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds real interpretive context beyond them: it warns that medianOpenPostingAgeDays is listing age rather than time to fill and removedRoles30d is takedowns rather than filled roles, which prevents misreading of the returned numbers.

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?

Front-loaded with purpose, then the metric caveats, then the URL. The 'hiring.definitions says...' phrasing is slightly opaque (it reads as a field reference inside the response), but no sentence is filler.

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-only lookup with no output schema and full annotation coverage, the description supplies everything needed: the input's origin, the scope of returned content, and a semantic warning about two easily misread hiring metrics.

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 coverage is 0% and the single parameter carries only type and length bounds, so the description must supply meaning — it does by defining slug as the employer slug and mapping it to companySlug on a job record, plus showing the page URL pattern. It stops short of case/format normalization rules.

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 an employer's profile by its slug') and enumerates the profile contents: size, pay bands, work arrangement, benefits, recent events, hiring. That enumeration implicitly separates it from get_job and list_company_jobs, though no sibling is named explicitly.

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?

Provides a useful anchor for the input ('companySlug on a job'), which implies the caller arrives from a job record, but gives no explicit when-to-use vs. when-not guidance and never routes the agent to list_company_jobs or search_jobs for the alternatives.

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