github_list_org_invitations

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

With no annotations provided, the description carries the full burden for behavioral disclosure. However, it only mentions the parameters and their defaults, which are already in the schema. It does not disclose whether the operation is read-only, any authorization requirements, rate limits, or pagination behavior beyond the parameter descriptions.

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 and front-loaded with the primary purpose, followed by a clear, structured Args block. No redundant text is present, and every sentence contributes to understanding.

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 simple list operation with an output schema, the description sufficiently covers purpose and parameters. It could add context about when to use this versus invitation creation/cancellation, but the core information is present. The output schema exists, so return values do not need to be explained.

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 schema has no property descriptions (0% coverage), so the description compensates by explaining each parameter's purpose, including the max value for per_page and defaults. This adds meaning beyond the schema's basic type/default information.

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 'List the organization's pending member invitations' with a specific verb and resource, distinguishing it from sibling tools like creating or cancelling invitations. It leaves no ambiguity about the tool's function.

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 purpose implies usage for viewing pending invitations, but there is no explicit guidance about when to prefer this over alternatives or any exclusions. The description does not mention scenarios where other invitation-related tools should be used instead.

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