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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing the 300-job cap, the confidence semantics ('high means the website links to the board; unverified means only the name matches'), rate limits, per-result pricing via x402 on Base, and a genuinely important billing nuance (no board or no open jobs is never charged).

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?

Dense but front-loaded, leading with purpose and source coverage before pricing and confidence caveats. Every clause carries information (sources, cap, diff behavior, pricing), though the pricing sentence is long and could be split for readability.

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 an output schema present, return-format details are unnecessary, and the description still supplies everything else an agent needs: cost model, caps, confidence interpretation, and diff mechanics. Nothing material is missing for correct invocation.

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 the baseline is 3, but the description adds relational meaning the schema does not fully express: the dependency that diff_only requires known_job_ids, and that supplying known_job_ids causes the response to list new and closed job IDs.

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?

States a specific verb and resource ('live open jobs for a company domain') and enumerates the exact board sources (Greenhouse, Lever, Ashby, Workable, Recruitee, SmartRecruiters), so the agent knows precisely what is returned. It does not, however, distinguish itself from the closely related sibling get_company_hiring_intent, leaving the agent to infer which to pick.

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?

Provides clear usage context ('hiring signals for sales, recruiting and research agents') and operational guidance for the diff workflow ('send known_job_ids to get new and closed jobs; diff_only returns only new ones'). It lacks explicit when-not/alternative routing versus sibling tools like get_company_hiring_intent or company_footprint_check.

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