github_orgs_remove_member

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

The description indicates a destructive action ('remove') but provides no details on side effects, required permissions, or reversibility. Without annotations, the description carries full burden and is insufficient.

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, concise sentence with no wasted words. It is appropriately sized for a simple tool.

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 many sibling tools with similar names (e.g., remove_membership, remove_outside_collaborator), the description lacks necessary context to disambiguate. It does not explain what 'remove an organization member' entails or how it differs from other removal operations.

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?

Schema coverage is 100%, so baseline is 3. However, parameter descriptions are trivial ('org', 'username') and the tool description adds no further meaning. The description does not compensate for weak parameter documentation.

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 states 'Remove an organization member', which is a clear verb+resource. However, it does not differentiate from sibling tools like 'github_orgs_remove_membership_for_user' or 'github_orgs_remove_outside_collaborator', which have overlapping purposes.

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 on when to use this tool versus alternatives. No mention of prerequisites, permissions, or context in which removal is appropriate.

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