list_invitations_sent

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

No annotations exist, so description is key. It indicates listing returns a list with recipient details but does not disclose read-only nature or other behavioral traits like idempotency. Adequate but minimal.

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?

Extremely concise with no wasted words. Front-loaded purpose, then parameter explanations, and return description. Every sentence adds 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?

Adequate for a simple list tool with pagination. However, no output schema and no mention of sorting or filtering. With no annotations, additional context like rate limits or result structure would improve completeness.

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 has 0% description coverage, but the description explains limit as 'Max results per page (default 50)' and cursor as 'Pagination cursor from previous response,' adding meaning beyond types and defaults.

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?

Clearly states 'List pending outbound connection requests,' identifying the verb and resource. Distinguishes from sibling tool list_invitations_received by specifying 'outbound'.

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?

Implies usage for viewing sent invitations but lacks explicit when-not or alternative comparisons. With siblings like accept_invitation and list_invitations_received, more guidance would help.

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