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

The annotations only provide readOnlyHint and openWorldHint, while the description adds meaningful behavioral context: public/logged-out scope, 10 results per page, omitted fields, pricing, payment rails, and the fact that failed calls are not charged. No annotation contradiction is 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?

The description is two compact sentences with no wasted language. It front-loads the core scope and then adds limitations and pricing details efficiently.

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?

Given the output schema and annotations, the description supplies enough context to call the tool correctly: source scope, returned fields, exclusions, pagination behavior, and billing behavior. Nothing essential for 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%, with keywords, location, and page fully documented in the schema. The description echoes keyword/location usage and the 10-per-page limit but does not add syntax, defaults, or constraints beyond what the schema already provides.

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 names the specific source and resource: LinkedIn job postings from LinkedIn's public logged-out job search. It also enumerates the returned fields and pagination, which clearly distinguishes it from sibling job-board tools by data source and scope.

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?

It implies when the tool is appropriate by specifying the public logged-out LinkedIn source and listing exclusions such as job descriptions, salaries, and applicant counts. However, it does not name alternatives or explicitly state when to choose this over sibling tools like jobs_indeed or jobs_glassdoor.

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