LinkedIn posts

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

No annotations are provided, so the description carries the full burden. It only says 'structured data' with no disclosure of behavior, output format, authentication needs, rate limits, or what happens on invalid URLs. This is essentially no transparency.

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 extremely short (five words) but under-specified. It is not concise in an effective way—it omits essential information and reads more like a fragment than a functional description.

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 or annotations, the description must explain what 'structured data' means (fields, format, etc.), but it does not. The tool's purpose, return value, and behavior are all unclear, leaving the agent without sufficient context.

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% (the single 'url' parameter is described as 'LinkedIn post URL'). The tool description adds no additional meaning beyond the schema, so the baseline of 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?

The description 'Structured LinkedIn post/article data' is a noun phrase without a verb, so it does not clearly state what the tool does (fetch, scrape, retrieve, etc.). It vaguely indicates the resource (LinkedIn posts/articles) but does not distinguish from siblings like job listings or profiles.

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 guidance on when to use this tool versus alternatives. No context, prerequisites, or comparison with sibling tools like web_data_linkedin_person_profile or web_data_linkedin_company_profile is provided.

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