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

Goes well beyond the supplied annotations by disclosing the access model (no login, no browser) and the billing model (1 credit per result, failed items free) — exactly the kind of operational context annotations do not carry. Combined with readOnlyHint/openWorldHint, an agent can judge both safety and cost before calling.

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?

Four compact clauses: what it searches, what it returns, access constraints, cost. The filter/return enumeration is front-loaded and no sentence is redundant.

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 three-parameter, no-output-schema tool, the definition covers return fields, cost, and auth requirements adequately. It is slightly thin on multi-search batching behavior and result ordering, but nothing critical to correct invocation is missing.

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 parameter meaning is already fully documented, establishing a baseline of 3. The description's only added semantic content is tying credit cost to results, while the per-search vs. total result caps and the includeDescription request overhead are all explained in the schema instead.

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 (search) and resource (LinkedIn job postings) and then enumerates both the filter dimensions and the returned fields, so an agent knows exactly what it gets. It does not explicitly contrast with indeed-jobs, but the LinkedIn scope in the name makes the platform boundary self-evident.

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 or when-not-to-use guidance, and no named alternative (e.g., indeed-jobs for non-LinkedIn postings). Usage is only implied by the enumerated filters; an agent must infer the routing decision entirely from the tool name.

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