harvest_get_company

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

With no annotations, the description must carry behavioral disclosure. It only states the input requirement and does not explain behavior when multiple parameters are provided, error handling, authentication needs, or return format. Minimal context beyond the basic action.

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, front-loaded sentence that states the action and the key requirement without any filler. Every word earns its place.

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 is simple with three optional parameters and no output schema. The description plus schema provide the essential information for a basic getter tool. Missing details like precedence when multiple params are given or what the response contains slightly reduce completeness.

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 coverage is 100% since each parameter has a description. The description adds value by specifying the cross-parameter constraint that at least one of the three must be provided, which is not enforced by the schema (all are optional). This helps the agent avoid invalid calls.

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: 'Get LinkedIn company' with a specific verb and resource. It distinguishes itself from sibling tools like harvest_search_companies by implying direct retrieval by identifier rather than search, and the requirement clause adds specificity.

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?

It provides a clear usage constraint: 'requires at least one of url, universalName, search.' However, it does not explicitly mention when to use this tool instead of alternatives like harvest_search_companies, leaving the comparison implicit.

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