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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so safety behavior is covered. The description adds useful scope information about including both received and sent pending requests, but does not disclose response shape, pagination, or any other behavioral details beyond that scoping.

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?

Two sentences with no filler. The core action and object are front-loaded, followed by concrete usage triggers and a pointer to the follow-up tool. Every sentence contributes value.

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 operation with strong annotations and a straightforward purpose, the description is complete. It tells the agent what is listed, when to use it, and how to continue the interaction, leaving no critical gap 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?

The tool has zero parameters and the schema coverage is trivially complete, so the description has no parameter semantics to add. The baseline for zero-parameter tools is 4, and the description appropriately relies on the implicit signed-in user context rather than introducing parameters.

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 clearly identifies the resource: connection requests for the signed-in user, both incoming and outgoing pending ones. It is distinct from sibling tools like respond_to_connection, which handles acting on requests, and my_bookings, which covers a different domain.

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 gives explicit triggers: 'when the user asks who wants to connect, or what is waiting on Foundaree.' It also points to the relevant sibling, respond_to_connection, as the next action, providing routing guidance beyond a simple listing.

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