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

The readOnlyHint and openWorldHint annotations already tell the agent this is a safe, external read. The description adds no behavioral context such as pagination behavior, ordering, or limits, so it does not go beyond the structured hints.

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?

It is a single front-loaded sentence with no wasted words, which is structurally clean. However, it is arguably too thin for a three-parameter listing tool, so brevity here reflects under-specification as much as conciseness.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. But with 0% parameter coverage and a required company identifier, the description should at minimum clarify what 'company' means; it leaves an agent without enough to call the tool confidently.

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% for all three parameters. The description only implies that 'company' scopes the listing; it says nothing about limit/offset pagination semantics or what form the company identifier should take, so it fails to compensate for the schema gap.

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?

The description names a specific resource ('postings') and scope ('for a company') on the SmartRecruiters platform, so an agent knows it lists job postings rather than fetching one. It does not explicitly contrast with the singular sibling jobs_smartrecruiters_posting or other job-board tools, relying on the name to differentiate.

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?

There is no when-to-use guidance, no conditions, and no named alternative. The phrase 'for a company' hints that the company parameter is required, but the description never says when to pick this over jobs_smartrecruiters_posting or the many other jobs_* siblings.

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