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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered by structured data. The description adds one real behavioral fact beyond that: the result set is filtered to companies with open jobs, which affects what the caller will receive. It says nothing about pagination behavior or result ordering despite the tool having page/limit controls.

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, no filler, with the filtering constraint front-loaded. Every word earns its place and there is no redundancy with the title or schema.

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 simple read-only listing tool with annotations covering the safety profile and no output schema, the description is close to sufficient: the resource and its filter are clear. The only meaningful gap is pagination semantics, which matter given the tool returns a capped, paged list.

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 0%, and the description never mentions the page or limit parameters, their defaults (1 and 10), the limit cap of 20, or that results are paginated. With two undocumented parameters and no compensating text, an agent learns nothing about controlling result volume from the definition.

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 (List) and resource (companies) with a meaningful scope qualifier — only companies that currently have open jobs. This cleanly separates it from get_company (single company lookup), but it does not explicitly position itself against search_jobs or get_job, which it could reasonably be confused with when an agent wants job-related data.

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?

The scope phrase 'currently have open jobs' implicitly tells an agent when this is appropriate (discovering employers with active postings), but there is no explicit when-to-use versus when-not-to-use guidance and no named alternative among the siblings. Usage is inferable rather than stated.

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