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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and open-world scope are covered structurally. The description adds only that all jobs are returned in 'one normalized jobs schema', which is a useful but thin behavioral detail — there is no mention of pagination, per-site coverage limits, timeouts, or cost on a multi-board crawl.

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 content is short, but the first sentence is cut off mid-list ('Greenhouse, Lever…') and then immediately repeated in full — duplicated, truncated boilerplate that wastes the opening position and reads as an extraction artifact rather than deliberate front-loading.

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 no output schema, the description should say more about what a normalized jobs record contains and how the opaque nested 'input' object (whose docs live off-site) is shaped. It leaves both the return payload and the required input configuration unexplained for a multi-platform crawl.

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?

There is a single top-level parameter whose schema description is only a pointer to an external URL, so the description adds no parameter meaning of its own. Per the high-coverage baseline this lands at 3, though the schema's nominal 100% coverage is effectively a link rather than real documentation.

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 states a specific verb and resource — 'scrape every open job from company career sites' — and enumerates the ATS platforms covered (Greenhouse, Lever, Ashby, Workday, SmartRecruiters), which is concrete enough to separate it from generic scrapers. It does not, however, name or contrast itself against adjacent siblings like b2b_job_post_parser or b2b_hiring_signal_tracker.

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 prerequisites, and no named alternative for cases where a user wants a single company's jobs or a non-career-site source. The agent must infer usage entirely from the purpose sentence.

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