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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and network profile is covered. The description adds the aggregation framing (derived signals rather than raw postings) but says nothing about auth/token requirements even though a 'token' parameter exists, nor about rate limits or caching. Minor added value with a notable gap.

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 front-loaded sentence with no filler; appropriate size. It is efficient, though its brevity partly reflects under-specification rather than disciplined editing.

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 10 parameters, 0% schema coverage, and an existing output schema, the description should at least explain how to pick the provider and identify the board. It does neither, and it never clarifies what 'hiring signals' actually returns. Inadequate for the tool's complexity.

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% across 10 parameters. The phrase 'a company's ATS board' loosely hints at company/org/board/provider, but host, site, token, domain, tenant, and datacenter are undocumented in both schema and description. With this many undocumented provider-specific identifiers, the description fails to compensate.

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 gives a verb+resource ('Aggregate hiring signals') from an ATS board, which is more specific than the bare name. However, 'hiring signals' is never defined, and it does not distinguish itself from the many sibling board/posting tools (jobs_greenhouse_board, jobs_lever_postings, jobs_ashby_board). An agent cannot tell what unique output 'signals' produces versus listing postings.

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 statement of when to use this tool versus the dozens of sibling jobs_* tools, nor any prerequisites or conditions. The agent is left to infer usage entirely from the name.

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