enrich_member_posts_with_engagement

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

With no annotations provided, the description carries full burden for behavioral details. It mentions 'when scopes are available' implying authorization, but does not disclose side effects, error conditions, or whether the operation is read-only or modifies state.

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 sentence of 13 words, which is concise. However, it sacrifices necessary detail; it is not appropriately sized for a tool with 6 parameters and no other structured metadata.

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?

Given the tool has 6 undocumented parameters, no output schema, and no annotations, the description is severely incomplete. It does not cover expected output, error conditions, or relationship to sibling tools like list_member_posts.

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 0% and the description does not explain any of the 6 parameters. An AI agent would have no context on how page_size, limit, published_after, social metadata flags, or analytics metric types affect the enrichment.

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 the action ('Enrich exported member posts') and the type of data added ('LinkedIn social metadata and analytics'). It distinguishes from sibling tools like get_member_post_analytics and get_post_social_metadata by implying a combination of enrichment, but does not explicitly differentiate.

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 description provides no guidance on when to use this tool versus alternatives, nor any prerequisites such as requiring exported posts or specific scopes. The phrase 'when scopes are available' hints at authorization but is vague.

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