linkedin_generate_boolean_search

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says the tool 'generates' search strings and gives no detail about side effects, network usage, output format, or whether anything is persisted. This leaves behavioral expectations vague.

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 with no filler. It efficiently communicates the action, output type, and target surfaces, even though the word 'optimized' is somewhat imprecise.

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?

There is no output schema and no clarification of whether the tool returns a single string, multiple strings, or an object. Given the absence of annotations and output schema, the description should provide more detail about the return format and behavior to be fully complete.

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 schema descriptions cover 100% of the parameters with meaningful labels like 'Decision maker job titles', 'Target service/niche keywords', and 'Exclusion keywords'. The tool description itself adds no parameter-level meaning, but the schema already carries the load.

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 ('Generates'), a concrete output type ('Boolean search strings'), and three target surfaces (LinkedIn People Search, Company Search, Google X-ray). It clearly conveys what the tool does, though it does not explicitly differentiate it from close siblings like linkedin_build_lead_search.

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 implies usage when Boolean search strings are needed, and specifies the target platforms, but it gives no explicit when-to-use or when-not-to-use guidance. With many LinkedIn siblings, naming alternatives or exclusions would improve tool selection.

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