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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior the annotations do not: the personal-profile default, and the precondition that a page-scoped urn must belong to that page.

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, front-loaded with purpose, then default behavior, then the page constraint. Every sentence carries information and nothing is repeated from the annotations.

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 still says what is returned (text, metrics, simplified media) and covers both targeting modes plus the urn/page relationship. An agent has everything needed to call this correctly.

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 baseline is 3, and the organization parameter is already documented as optional in the schema. The description rises above baseline by stating a cross-parameter constraint (a company-page urn must belong to the targeted page) that the schema does not express.

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 ("Retrieves the full details of a LinkedIn post") and enumerates the payload (text, metrics, simplified media), which is enough to separate it from siblings like get_post_likers, get_post_commenters and get_posts_stats_summary without opening a schema.

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?

Explains the default target (personal profile) and the condition that switches to a company page, pointing at list_organizations as the source of the organization value. It gives clear usage context but offers no explicit when-not-to-use or alternative sibling to call instead for a lighter read.

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