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

With no annotations, the description carries the full behavioral burden and does so well: it discloses the exact credit cost (7, cached or not), that failed calls are refunded, that group posts are unavailable, and the mutual-exclusivity of the two identifiers — all non-obvious operational facts an agent needs before calling.

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?

Three sentences, front-loaded with what is returned, then the limitation, then the input rule and cost. Efficient overall, though the long enumeration of returned fields could be tightened slightly.

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 read with no output schema and no annotations, the description covers returned fields, input constraint, cost, refund policy and cache behavior. Minor gaps remain — e.g. how `members` is returned (count vs list) and any rate limits — but nothing critical for correct invocation.

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 baseline is 3, but the description adds a constraint the schema does not express: `url` and `id` are mutually exclusive and exactly one must be given (required array is empty, so the schema alone does not enforce this). It adds real semantic value for the identifier choice.

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 (Fetch) and resource (one group) and enumerates the fields returned (name, members, description, rules, creation date, post visibility), letting an agent distinguish it from get_linkedin_posts or search_linkedin_groups without opening the schema.

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 clear context: this is a single-group lookup requiring exactly one of `url` or `id`, and it flags that group posts are not yet available via linkedin/posts. It does not explicitly name the scenario where searching (search_linkedin_groups) is preferred, so it stops short of full when/when-not guidance.

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