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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety and scope profile is covered. The description adds the filterable dimensions but says nothing about return format, pagination behavior, or credit cost. With annotations bearing most of the burden, this is adequate but thin.

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?

A single front-loaded sentence with the usage trigger first and the supported search modes following. Efficient with no redundant padding, though it is minimal enough that slightly more detail could still have fit.

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 an output schema and full annotation coverage, so return values and safety needn't be explained. Given those aids, the description is sufficient for a search tool, though it omits any mention of pagination or the credit/multi-turn conversation mechanics that the schema handles.

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 schema fully documents all 10 parameters including pagination_token, conversation_id, and the company/company_name alias. The description only echoes the filter categories already in the schema, adding no meaning beyond it. Baseline 3 applies.

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?

States a specific verb ('find') and resource ('LinkedIn ads') plus the three search dimensions (company name, keyword, company ID), which cleanly separates it from the Google/Meta/TikTok search siblings by platform. It stops short of explicitly differentiating from get_linkedin_ad_details (search vs. detail lookup), so it isn't fully sibling-resolved.

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?

Opens with 'Use this when you need to...' and describes the trigger conditions and optional filters, giving clear context for invocation. It never states when NOT to use it or names an alternative tool (e.g., get_linkedin_ad_details), so it falls short of a 5.

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