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

With no annotations supplied, the description carries the full load and does well: it names the upstream data sources, discloses refresh cadence ('crawled twice a day'), and states the cost and payment rail ('$0.01 USDC on Base via x402'), which is critical behavioral context for an agent deciding whether to invoke a paid tool. It stops short of describing failure behavior (company not found, no job board detected) or output shape, which keeps it from a 5.

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 front-loaded with the user-facing question, then enumerates the payload, then closes with pricing so the cost is visible before the agent commits. The middle sentence is a dense comma list, but every item is a real data field being advertised. Slightly long, but no filler sentences.

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 one-parameter tool with no output schema and no annotations, the description covers most of what an agent needs: sources, freshness, cost, and an inventory of returned fields (careers page, open roles, departments, locations, remote share, pay median, newest jobs, 7/30-day opened and closed counts). The remaining gap is the absence of any differentiation from company_jobs/company_hiring_trend, which matters in a catalog of this size.

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 required parameter and the schema description coverage is 100%, already giving examples (openai, stripe.com, https://jobs.lever.co/palantir). The description's phrase 'from its public job board' reinforces that the input resolves to a company with a known ATS, but adds no format or resolution rules beyond the schema. Baseline 3 applies when the schema 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 opens with the concrete question it answers ('Is a company hiring?') and then states the resource precisely: a hiring profile built from named public job boards (Greenhouse, Lever, Ashby, Workable, SmartRecruiters, Recruitee, Workday) crawled twice a day. That is a specific verb+resource, well beyond a restatement of the name. It does not, however, distinguish itself from nearby siblings such as company_jobs, company_hiring_trend, or company_enrich, so a 4 rather than a 5.

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?

Usage is implied by the framing question: call this when you want an overall hiring snapshot of a specific company. There is no explicit when-to-use/when-not statement and no named alternative, despite three closely related sibling tools (company_jobs, company_hiring_trend, jobs_search) that an agent would need help choosing between. The implied context is clear but the routing guidance is absent.

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