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

No annotations are provided, so the description carries the burden of behavioral disclosure. It reveals that the tool lists only pending incoming requests, which is useful behavioral context. However, it does not mention whether the operation is truly read-only, how the list is ordered, or pagination behavior beyond the schema's cursor parameter. It adds some value but is not extensive.

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, front-loaded sentence with no unnecessary words. Every word serves to identify the purpose and scope of the tool. It is concise and effective.

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?

This is a simple list tool with two well-documented parameters and no output schema. The description clearly states what is listed and adds the important context that these are incoming and awaiting response. While it doesn't detail the return format, that is less critical for a list tool. The description is adequately complete for the tool's simplicity, though a note about pagination or count could add value.

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 coverage is 100% for both parameters (limit and cursor), including descriptions. The tool description does not add anything about how these parameters affect the results, but the schema already fully documents them, so a baseline of 3 is appropriate. The description's mention of 'pending incoming' does not change parameter semantics.

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 clearly states the tool's function: 'List pending incoming connection requests waiting for your response'. It uses a specific verb 'List' and a resource 'pending incoming connection requests', and the phrase 'waiting for your response' distinguishes it from sibling tools like social_connections or social_connection_status, which likely show all connections or a specific status.

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 description implies usage when the user needs to see incoming connection requests that require a decision (accept/decline). However, it does not explicitly name alternative tools or provide exclusions, such as when to use social_connections instead for a full list. The context is clear enough for a basic understanding but lacks direct comparative guidance.

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