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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds a genuinely useful behavioral fact not in the annotations: only postings owned by the account are returned. However, it says nothing about pagination behavior, result ordering, or caps (limit max 100, offset present).

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?

Three short sentences with zero filler; scope, purpose and sibling disambiguation are all front-loaded in the first two sentences.

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?

There is no output schema, so the description should carry more of the return story; telling the agent it yields job_posting_ids for management/budget operations helps, but nothing is said about pagination, state filtering semantics, or result shape.

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 coverage is only 25%; the only documented parameter is account_id. The description never explains state filtering (DRAFT/OPEN/CLOSED/REVIEW/SUSPENDED), the default all-states behavior, or how limit/offset pagination works, so it does not compensate for the coverage gap.

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 (List) plus resource (LinkedIn job postings) and a scope qualifier (OWNED by the user's account) that immediately distinguishes it from discovery-style listing. It also names the sibling it is not.

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?

Gives an explicit use case ('resolve job_posting_id for management/budget operations') and an explicit alternative with its own condition ('linkedin_search_jobs, which discovers jobs across LinkedIn'). The agent can pick between the two without opening either schema.

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