github_enterprise_team_memberships_bulk_remove

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

With no annotations, the description must convey behavioral traits but fails to do so. It does not disclose whether the operation is destructive, idempotent, or what happens if members do not exist. The body parameter's structure is left completely opaque, leaving the agent without crucial behavioral expectations.

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 short sentence, making it concise but overly terse. It lacks structure and fails to provide essential information, balancing brevity against completeness. It is not an example of efficient communication since it sacrifices clarity for shortness.

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 tool's complexity (multiple siblings, a body parameter) and the absence of an output schema, the description is critically incomplete. It does not explain what constitutes a 'team member', the expected format of the body, or any response behavior. The agent would lack sufficient context to use the tool correctly.

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's parameter descriptions are minimal ('enterprise', 'enterprise-team', 'Request body (JSON object)'), and the tool description adds no further meaning. The body parameter's expected properties are undefined, and the description offers no clarification, resulting in poor semantics.

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 'Bulk remove team members' reiterates the tool name with minor elaboration, providing a clear verb and resource but without additional context on scope or differentiation from sibling tools like '_bulk_add' or '_remove'. It is minimally adequate but does not enhance understanding beyond the name.

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 bulk removal tool versus the singular '_remove' or other sibling tools like '_add'. The description lacks any contextual cues for decision-making, such as prerequisites or scenarios where bulk operation is appropriate.

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