collaboration_user_repo_invitations

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

The description explicitly states read-only, which is positive for a tool with no annotations. However, it does not disclose details like pagination, rate limits, or behavior when no invitations exist, leaving some gaps.

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 wasted words, conveying the essential information effectively.

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?

Given no parameters and no output schema, the description is mostly complete. It could optionally hint at the structure of the return list (e.g., repository names, invitation status), but the core purpose is clear.

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?

No parameters exist, and schema coverage is 100%. The description adds value by specifying scope (current agent identity), which is not in the schema. Baseline for zero parameters is 4.

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 lists repository invitations pending for the current agent identity and explicitly marks it as read-only, distinguishing it from sibling tools like collaboration_repo_invitations or accept/decline tools.

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 for viewing one's own pending invitations before acting on them, but does not explicitly state when to use this tool versus alternatives like collaboration_repo_invitations (which might list all invitations) or when not to use it.

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