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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds two things beyond that: a platform restriction ('LinkedIn accounts only') and a quota/accounting signal ('Counts as browsing'), which is the kind of side-effect context annotations cannot express. It does not describe pagination behavior when results exceed the limit.

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 short sentences, front-loaded with the platform constraint and then the resource scope, with no filler. The telegraphic fragment style ('who sent them, their headline and any note') is efficient but slightly clipped.

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?

With no output schema, the description helpfully summarizes what each entry contains, which covers the return-value gap. However, for a paginated list tool it omits any mention of limit/cursor semantics or maximum page size, leaving an agent unable to plan iteration from the description alone.

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 0% across three parameters, so the description carries the full burden and mostly fails it. It never mentions limit, cursor, or account_id — 'this account' only vaguely gestures at account_id, and pagination via cursor/limit is entirely unexplained.

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 names a specific verb+resource (invitations waiting for this account) and enumerates the returned content (sender, headline, note), which separates it in spirit from the broader list_invitations sibling. It stops short of explicitly contrasting with that sibling by name, leaving the received-vs-sent distinction to be inferred from 'waiting for this account'.

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?

It gives clear usage context: only applies to LinkedIn accounts, and points the agent to respond_to_invitation for the follow-up action on a listed item. There is no explicit when-not guidance or statement about what to do when the list is empty, but the routing to the sibling action is genuinely useful.

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