invitations_list

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It discloses access restrictions (admin/owner only) and filters (pending only), which is useful and accurate. However, it does not describe return format, pagination, sorting behavior, or whether pending invitations are limited by time. The description adds moderate value beyond the name but leaves several behavioral questions unanswered.

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 two sentences with zero waste. The first sentence states the core purpose, the second adds the key filtering detail and authorization requirement. Every clause earns its place; there is no fluff or repetition.

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?

This is a simple zero-parameter list tool with no output schema. The description covers the essential filtering logic (pending only) and access control (admin/owner only). For a tool this simple, the description is largely complete; a small gap exists around whether any other implicit filters apply or whether pagination is a concern, but for a zero-parameter listing of pending invitations the provided information is adequate.

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 0 parameters, so the schema provides no information to add meaning to. With 0 parameters, the baseline is 4 per the rubric, and the description appropriately explains the fixed behavior (lists all pending, not yet accepted invitations). There are no parameter semantics to clarify since there are no parameters, and the description handles this well by clarifying the filtering behavior.

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 verb+resource: 'List all pending invitations for the organization.' It precisely defines scope (pending, not yet accepted invitations) and distinguishes from sibling tools like invitations_create, invitations_delete, and invitations_resend. The purpose 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?

The description provides clear context about what is returned (only not-yet-accepted invitations) and who can use it (org admins and owners). However, it does not explicitly mention when to use it versus alternatives, nor does it note that this is a read/query operation distinct from invitations_create/delete/resend. The when-not guidance is implied rather than stated.

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