github_repos_delete_invitation

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

The description gives no behavioral details beyond the action 'Delete'. It does not disclose side effects (e.g., notification sent, access revoked), required permissions, or irreversible nature. With no annotations provided, this is a significant gap.

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 sentence, very concise with no extraneous information. However, it is so terse that it sacrifices completeness, but for conciseness alone it scores well.

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 the lack of output schema and annotations, the description fails to provide sufficient context for a delete operation. It does not explain what happens upon deletion, any side effects, or prerequisites, leaving the agent underinformed.

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 input schema has 100% description coverage, but each description is just the parameter name (e.g., 'owner', 'repo', 'invitation_id'). The tool description adds no further meaning, failing to compensate for the schema's minimal descriptions. An agent gains no additional insight into parameter format or constraints.

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 'Delete' and the resource 'repository invitation', making the primary purpose clear. However, it does not differentiate from sibling tools like github_repos_update_invitation or github_repos_list_invitations, but the action itself is distinct enough.

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?

No guidance is provided on when to use this tool versus alternatives, nor any prerequisites like required permissions or conditions for the invitation to exist. This leaves the agent without context for appropriate usage.

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