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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so "Read-only" simply repeats structured data. The description adds nothing about pagination, result volume, rate limiting, or what the linkedIn-account scoping implies for results.

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 short and front-loads the resource, which is good, but the second sentence ("Read-only") is redundant with the annotations and does not earn its place. Brevity here reflects under-specification rather than discipline.

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 no output schema, 0% parameter coverage, and a nested untyped parameter, the full explanatory burden falls on the description, which supplies essentially nothing. An agent knows the resource name but not what it will receive or how to shape the "extra" parameter.

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 0% for two parameters, including a required UUID account_id and a free-form nested "extra" object with additionalProperties. The description says nothing about either parameter, so an agent gets no meaning for the open-ended "extra" bag or confirmation of what account_id selects.

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?

"Job posts on this LinkedIn account" identifies the resource (job postings) and its scope (the authenticated account), so the agent can infer this is a list operation, but the phrasing is a noun fragment that largely restates the tool name and title. It does distinguish implicitly from the singular get_job_posting only through the name, not through any description text.

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 guidance on when to use this tool versus get_job_posting for a single posting, or versus other list_* tools for related entities such as list_hiring_projects. The agent must infer usage entirely from the name.

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