get_post

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

With no annotations provided, the description carries the burden of disclosing behavior. The verb 'Get' implies a read-only operation, and the description adds specific context about the return value (whether the current account has liked or commented). It does not discuss authentication or error behavior, but for a simple getter the core traits are clear.

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 only two sentences long, front-loaded with the core action ('Get a LinkedIn post by URL'), and contains no redundant words. Every sentence adds value.

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 getter with no output schema, the description conveys the main purpose and a key return detail. It lacks explicit context about session prerequisites or error cases, but the full parameter schema and straightforward operation make it largely 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?

The input schema has 100% coverage for both parameters (post_url and profile_id), so the schema already documents their meaning. The description adds no additional information about parameter formats or usage beyond what the schema provides, hence the baseline score of 3.

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 clearly states a specific verb ('Get') and a specific resource ('a LinkedIn post by URL'), and it also describes what will be returned (post details including like/comment status). This distinguishes it from sibling tools like get_profile (fetches a profile) and read_feed (fetches feed posts).

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?

There is no explicit guidance on when to use this tool vs alternatives such as search_posts or read_feed. It does not mention prerequisites like having a valid session or cookies, nor any circumstances when this tool should be avoided.

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