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

Annotations already declare read-only, idempotent, non-destructive behavior, so the bar is lower; the description still adds real value by disclosing 'opens nothing by itself' and that the payload is a step-by-step guide with screens, buttons and fields. The note about LinkedIn's official API requiring an approved application explains why browser automation is the route. Minor gap: no statement of whether the guidance is current or how it handles a not-logged-in browser.

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 core disclosure ('returns how to do it step by step, opens nothing, then use cotlet_browser_*') is front-loaded and useful. However, 'from ChatGPT, Claude or any AI agent' is promotional padding, and the dated API aside, while mildly informative, competes with the primary instruction.

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 zero-parameter, no-output-schema guidance tool, the description covers what it returns, that it performs no action, and which tool family continues the workflow. Nothing essential for correct invocation is missing.

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?

Zero parameters, so the baseline is 4. The description correctly implies no inputs are required; nothing about parameters needs explaining.

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 and resource ('Search people in the user's own LinkedIn account') and immediately clarifies the non-obvious reality that it returns step-by-step instructions rather than performing a search. The resource framing ('people') implicitly separates it from linkedin_search_companies and linkedin_create_post, though it never explicitly names those siblings.

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?

Gives a clear usage path: call this to get the procedure, then execute it with the cotlet_browser_* tools in the user's LinkedIn Cloud Browser, which is a concrete pointer to the alternative tool family. It stops short of stating when NOT to use it (e.g. versus linkedin_list_connections for an existing connections list).

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