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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds valuable context about the ID provenance requirement and the scope of owned postings, which goes beyond the annotations and prevents misuse.

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 somewhat repetitive, restating the ID source in multiple places (main description and parameter description). It's front-loaded with the key constraint, but the redundancy could be trimmed without losing meaning.

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 simple get-one-posting tool with no output schema, the description is sufficient: it states what it does, how to obtain the required ID, and what not to pass. The lack of return-format detail is acceptable given the tool's low complexity and existing annotations.

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 100%, so both parameters are fully described. The description reiterates the job_posting_id guidance but doesn't add substantial new meaning beyond the schema, though it does emphasize the source constraint. Meets the baseline for high coverage.

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: 'Get one job posting owned by the user's LinkedIn account.' It clearly distinguishes from siblings like linkedin_list_job_postings (listing) and linkedin_search_jobs (searching) by explicitly scoping to owned postings and requiring a specific ID source.

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?

Provides explicit when-to-use guidance: the job_posting_id MUST come from linkedin_list_job_postings, not a title/company or unrelated discovery. It also gives the exact workflow for obtaining the ID from both search and list endpoints, and warns against passing job title or company ID.

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