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

Annotations cover the safety profile (readOnlyHint, destructiveHint=false, openWorldHint). The description goes beyond them by disclosing return contents (post text, author, images, videos, engagement metrics), pagination granularity, and per-request pricing ($0.006) plus the sentiment surcharge — cost information an agent cannot get from structured fields.

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 tight sentences: capability first, then return payload, then pagination and cost. Every sentence carries information and nothing is padded.

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, the description correctly describes the return payload, and it covers pagination and cost. Minor gaps remain: no note on auth requirements, rate limits, or whether the URL must be a canonical full page URL, but for a simple read endpoint this is close to complete.

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 documents url, page, and get_sentiment in detail. The description restates '10 posts per page' and the engagement metrics but adds no syntax, format, or constraint detail beyond the schema. Baseline 3 applies.

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 with scope qualifier: 'Get recent posts from a LinkedIn company page by URL.' This cleanly separates it from linkedin_company_details (page metadata), linkedin_person_posts (a different author type), and linkedin_post_details (single post).

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?

Usage is implied by the resource description ('posts from a company page'), but there is no explicit when-to-use/when-not guidance and no routing to alternatives such as linkedin_post_details for a single post or search_linkedin_companies for finding the page URL. Adequate but leaves selection to inference.

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