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

Annotations only say readOnly/non-destructive, but the description adds real behavioral context: no email is sent by the tool, no email address is accepted as input, the user must open the link and confirm on veritahire.com themselves, and results stay live on employers' own careers sites. That is valuable beyond the annotations. It stops short of saying what happens on repeat calls (duplicate links vs. idempotent) or how long the link remains valid.

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 key outcome — returns a link — is front-loaded in the first clause, and the paragraph is short. The closing disclaimer ('sends no email and takes no email address' / 'only emails the address the person types there') is mildly redundant, costing a little tightness.

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 tool with five mostly undocumented parameters and no output schema, the description covers the conceptual outcome but leaves parameter behavior and the returned value's shape (URL only? any expiry metadata?) unaddressed. Adequate to call it, but not complete.

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 are five parameters but schema description coverage is only 20% (only 'where' is documented), and the description explains none of them — not 'what', 'remote_only', 'radius_miles', or 'employment_type', nor that all parameters are optional. 'Matching this search' hints the parameters define the saved search but adds no syntax or semantics the schema lacks.

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 concrete outcome: it returns a link that, once the user confirms their email on veritahire.com, yields a daily email of new jobs matching the search. That is a specific verb-plus-resource and clearly different from a one-off job search. It does not name search_live_jobs or other siblings explicitly, so differentiation is inferred from the outcome rather than stated.

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 only implied: 'matching this search' suggests this is the follow-up to a search the person already ran, and the link/confirm flow describes the after-step. There is no explicit when-to-use, when-not-to-use, or named alternative among the siblings such as search_live_jobs versus request_full_report.

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