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

With annotations covering readOnly=false, idempotent=false, and openWorld=true, the bar is lower, yet the description still adds real behavior: an external email is sent, clicking creates a free VeritaHire account, and nothing further is sent unless the link is clicked. That account-creation side effect and the single-send guarantee are meaningful disclosures beyond the structured hints. It omits failure modes and rate limits, keeping 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 action in the first sentence and spends the rest on report contents and the free/no-follow-up terms. The middle sentence is a dense run-on list of report fields, but every clause carries information an agent would not otherwise have. Reasonably sized for the amount it conveys.

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 7-parameter tool with 14% schema coverage and no output schema, the definition should resolve which parameters actually identify the posting and whether email alone is sufficient. It never does, leaving the agent unable to tell whether a bare email call is valid or will produce a report for the wrong posting. Behavioral outcome is well covered; call construction is not.

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 only 14%: just 'email' is documented, while city, state, title, job_id, job_url, and employer are bare. The description says the link goes to 'the work address given' and refers to 'that posting,' implying posting identifiers drive the report, but it never clarifies which of the six undocumented parameters are needed or optional. With coverage this low, the description must compensate and does not.

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 effect: it emails one link to a work address, and the click opens the full Competitive Hiring Report for a posting. The enumeration of report contents (employers within 25 miles, pay, fill speed, pay changes) makes the output's nature unmistakable. It does not explicitly contrast itself with compare_job_posting, hiring_market, or is_job_still_open, so it stops short of 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?

The description explains what the report contains and that it is free, but never says when to prefer this tool over its siblings or what conditions make it appropriate. There is no guidance on prerequisites such as which posting identifiers are needed before requesting a report. The closest thing to guidance is the 'first report is free' note, which is a commercial fact rather than usage direction.

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