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

With no annotations, the description carries full burden, and it does disclose the credit cost, which is a meaningful behavioral trait. However, it omits result shape, pagination, and whether results are live or cached. Worse, the flat claim 'Costs 5 credits per call' slightly conflicts with the schema's note that cached results are returned free unless refresh is true.

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?

Two short sentences, front-loaded with the purpose and immediately followed by the value proposition and cost. No filler, though the cost sentence would have earned more if qualified with the cache caveat.

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?

No output schema exists, so the description should at least hint at what a result looks like and how many are returned; it does neither. The rich parameter schema covers inputs well, but for a paid search call the description leaves the agent guessing about result shape and cost conditions.

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 schema already explains keywords, location, companyId with its ID-resolution caveat, sortBy, postedLimit, and refresh semantics. The description adds nothing beyond the mandatory-parameter baseline, which is acceptable but earns no extra credit.

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 ('Search LinkedIn job postings'), which distinguishes it from the many linkedin_* siblings that cover people, companies, posts, and ads. It stops short of naming or contrasting any specific sibling, so an agent must infer the split from the resource noun alone.

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?

'Useful for tracking hiring signals at target companies' gives one motivating use case but no when-not conditions, no prerequisites, and no named alternatives (e.g. linkedin_company_posts vs this for headcount signals). Usage has to be inferred from the resource name.

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