get_pending_invitations

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

With no annotations, the description carries the burden of conveying behavior. It indicates a read-only listing action and scopes it to the caller's account, but it does not mention whether authentication is required or whether any read-side effects such as marking items as seen could occur. These are unlikely for a list tool, so the lack is not severe.

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 description is a single, compact sentence with no filler. The key scope ('pending incoming', 'received by your account') is front-loaded and every word adds meaning.

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 read-only listing tool, the description fully explains what the tool does and what it does not cover. An output schema is present, so the return shape does not need to be spelled out in the description. No critical calling context 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?

The input schema has zero parameters, so there is nothing for the description to explain. The only relevant scoping information, 'your account', is provided in the description itself, satisfying the baseline for a parameterless tool.

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 uses a specific verb ('List') and a specific resource ('pending incoming connection invitations received by your account'). The 'incoming' and 'received by your account' wording clearly distinguishes it from sending requests or managing existing invitations.

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 phrase 'pending incoming' implies the tool is for viewing unanswered invitations addressed to the caller, which gives some context. However, it does not explicitly name alternatives such as manage_invitation or send_connection_request, nor does it state when not to use this tool.

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