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

With no annotations, the description carries the burden and does well: it discloses the 7-credit cost (incurred whether cached or not) and that failed calls are refunded. It also discloses page size and return fields, though it omits auth requirements and the credit/pack nuance that only appears in the schema for `fresh`.

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 a colon-delimited field list; almost every clause carries information. Minor density cost from packing return fields, pagination, and billing into one run-on line.

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, so the description's enumeration of returned fields and page size is valuable, and the cost/refund note covers a key operational concern. Cursor-based pagination is handled by the schema, leaving little materially 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?

Schema description coverage is 100%, so query, fresh, and cursor are already fully documented. The description adds only the page size ('10 a page') and implies keyword semantics for query, which is the baseline expectation when the schema does the heavy lifting.

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 groups) scoped by keywords, and enumerates the returned fields (name, URL, members, summary). It is clearly distinguishable from the sibling get_linkedin_group, which fetches a single group.

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 keyword-based search framing implies the use case (discovery vs. lookup), but there is no explicit when-to-use guidance and no mention of the alternative get_linkedin_group for single-group retrieval. Usage is inferable but not stated.

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