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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds real behavioral context beyond that: results are newest-first, each carries a link to the original post, the poster is often the hiring manager, and an extra X search link is returned.

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?

The description is front-loaded with the core scope and the source list, and every clause carries information. It is mildly repetitive, restating 'posts from people saying they're hiring' from the title at the start and again mid-paragraph.

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 low-complexity, read-only, 3-optional-param tool with no output schema, the description covers sources, ordering, link presence and the extra X search link. It does not state that all parameters are optional (i.e. calling with no arguments returns the newest hiring posts), which is the one gap.

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 100%, so what/where/limit are already fully documented in the schema. The description adds only loose semantic color (free-text field/city examples overlap with the schema), so this sits at the baseline for a schema that does the heavy lifting.

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 concrete resource ('public posts from people saying they're hiring') and its sources (Hacker News Who-is-hiring thread, Mastodon, Bluesky), which lets an agent separate it from generic job-board tools like search_jobs. However it never explicitly distinguishes itself from the close sibling jobspotter_whats_hiring, leaving the agent to infer the boundary.

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?

It gives concrete usage context through example queries ('who's posting that they're hiring React developers?', 'any startups hiring remote designers?'), which clearly frames the intended request shape. It stops short of when-not guidance or naming alternatives such as search_jobs/whats_hiring.

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