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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuine context beyond that: results are paged at 20 per record set and the response carries aggregate hiring data (open count, skills, median stated pay), which matters because there is no output schema. It does not mention what happens for an unknown company or whether paging past the last page errors.

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 dense sentence with zero filler, front-loading the scope ('one employer') before pagination and payload details. Nothing is repeated from the schema or annotations.

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 two-parameter, read-only lookup with no output schema, the description covers scope, page size, and the shape of returned data, which is the bulk of what an agent needs. Minor gaps remain around unknown-company behavior and pagination exhaustion.

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 50%: `company` has an example, `page` has only bounds and a default. The description clarifies that `company` means a single employer and that each page yields 20 jobs, which gives the page parameter practical meaning. It still does not say how many pages typically exist or how the page interacts with the 50 maximum.

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-less but precise resource: 'One employer's open tech jobs', scoped to a single employer, which implicitly separates it from search_jobs and match_my_skills. It also enumerates the payload (open count, skills, median stated pay). It never names a sibling explicitly, so differentiation is inferred 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?

'One employer's' implies the use case: look up jobs for a named company rather than searching broadly. There is no explicit when-to-use, when-not, or routing statement pointing at search_jobs or get_job, so the agent must infer the boundary.

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