Who else can reach this project

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

The description explains what a collaborator can do, but it does not disclose potential errors, return format, or side effects. With no annotations, the description carries the full burden and is insufficient for full transparency.

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 concise, using a few short sentences without fluff. It conveys the essential information efficiently.

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?

The description implies the output contains a list of collaborators and invite links, but it does not detail the output structure or handle edge cases. For a simple listing tool, this is adequate but not comprehensive.

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 parameter 'game' is already described in the schema as 'Game name or universe id.' The tool description adds no further clarification or context.

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 indicates that the tool lists collaborators and open invite links, and it notes owner-only access. While the verb 'list' is not explicit, the meaning is unambiguous.

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?

It states 'Owner only', which provides a usage constraint, but does not compare to sibling tools like list_projects or get_notification_history, nor does it mention when to use this versus alternatives.

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