harvest_search_groups

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

No annotations are present, so the description must carry the behavioral burden. It only states a search action without mentioning pagination, result limits, search matching behavior, authentication, or output format. For a search tool, such details are important but omitted.

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, short sentence with no fluff. It front-loads the action and resource, making it highly scannable and efficient.

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 simple search tool with two documented parameters and no output schema, the description is functionally adequate but feels thin. It does not explain what the response contains or whether pagination is required, yet the tool's simplicity lowers the risk of misuse. Overall, it is minimally sufficient.

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?

The input schema covers both parameters with descriptions ('Page number (default 1)' and 'Keywords to search for'), so schema coverage is 100%. The tool description adds no extra meaning beyond the schema; it only paraphrases the keyword parameter.

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 is very clear: 'Search LinkedIn Groups by keywords.' It uses a specific verb ('search') and a specific resource ('LinkedIn Groups'), distinguishing it from sibling search tools for ads, companies, jobs, profiles, etc. The purpose is immediately understandable.

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 does not provide explicit when-to-use guidance or alternatives. However, the resource name 'Groups' implicitly signals its use case compared to siblings. No exclusions or contextual hints are given, but the purpose itself offers basic guidance.

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