openai_delete_invite

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

With no annotations, the description carries the full burden. It discloses the important restriction that accepted invites cannot be deleted, which is valuable. However, it does not mention what happens if the invite is already revoked, whether the operation is idempotent, or any permission requirements, so transparency is moderate.

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. Each sentence earns its place, including the constraint and the parameter hint. No wasted words.

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 delete operation with one parameter and an output schema, the description covers the essential behavioral constraint (accepted invites cannot be deleted) and how to find the ID. It does not detail error behavior or success/failure formats, but the output schema likely covers that, and the tool is straightforward.

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 provides no description for invite_id, but the description explains it as 'The invite's ID' and points to openai_list_invites for retrieval. This adds meaning beyond the schema and is sufficient for a single parameter.

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 action (revoke) and resource (a pending invite), distinguishing it from other invite-related tools like openai_get_invite or openai_invite_user. It also adds a key constraint: accepted invites cannot be deleted, which further clarifies the tool's scope.

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 explicitly notes that accepted invites cannot be deleted, telling the agent this tool is only for pending invites. It also references openai_list_invites for finding the invite ID, providing a usage hint. However, it does not explicitly name alternatives or exclusions beyond the accepted-invite case.

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