get_linkedin_posts

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

No annotations are provided, so the description carries the behavioral burden. It adds useful scope context ('user's' and 'recent'), implying a read-only, date-recent retrieval. However, it does not disclose return format, ordering, pagination, authentication needs, or what exactly counts as 'recent'.

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 a single, focused sentence with no filler. It front-loads the action and resource and is easy to parse at a glance.

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 one-parameter read-only tool with no output schema, this is minimally adequate: an agent can invoke it with just limit. But gaps remain around expected response structure, what 'recent' means, and whether additional authorization or pagination is involved.

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 only parameter, limit, is already fully documented in the schema as 'Maximum number of posts to retrieve (default: 10)'. The description adds no additional parameter meaning, so the baseline 3 is appropriate.

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 states a specific verb ('Get') and resource ('the user's recent LinkedIn posts'). It clearly distinguishes itself from sibling tools: no other LinkedIn sibling retrieves posts, and get_linkedin_profile/get_linkedin_connections target different resources.

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?

The intended use is implied: call this when the user's recent LinkedIn posts are needed. However, the description provides no explicit when-to-use guidance, exclusions, or mention of alternatives, though no sibling directly overlaps with this function.

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