harvest_get_company_posts

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states an input requirement and does not mention pagination behavior, rate limits, return format, or any side effects. The lack of disclosure beyond the prerequisite leaves significant behavioral aspects undocumented.

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, front-loaded with the purpose, and includes an essential constraint. Every word earns its place; there is no unnecessary verbosity or repetition.

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?

The tool has 7 parameters, no output schema, and no annotations, but the schema descriptions are thorough. The description adequately covers the core purpose and the identifier requirement, but it omits any guidance on pagination flow, date filtering nuances, or what the response contains. It is minimally viable but not rich.

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. The description adds value by specifying that at least one of company, companyId, or companyUniversalName is required, which is not encoded in the schema (all parameters are optional). This clarifies the parameter selection logic beyond the schema descriptions.

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 tool's function: retrieving LinkedIn company posts. It uses a specific verb ('Get') and resource ('LinkedIn company posts'), distinguishing it from sibling tools like harvest_get_profile_posts or harvest_search_posts. The mention of required identifiers further clarifies the target.

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 a necessary prerequisite (at least one of company, companyId, companyUniversalName) but does not explain when to use this tool instead of alternatives like search_posts or get_post. The usage context is implied by the tool name and description, but no explicit exclusions or alternative guidance is given.

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