github_enterprise_team_organizations_bulk_remove

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

With no annotations provided, the description carries full burden for behavioral context. It only states the action but does not disclose whether it is destructive, required permissions, rate limits, or what 'bulk' entails (e.g., whether multiple organizations can be removed in one call). The description lacks essential behavioral cues.

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 extremely concise (two words) but at the expense of completeness. For a tool with a nested body parameter and bulk semantics, the description underspecifies. It is not appropriately sized for the complexity involved.

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 is grossly incomplete. It fails to explain the body parameter format, the bulk behavior, return values, or success/error conditions. An agent would struggle to use this tool correctly without additional information.

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 parameter descriptions are just names ('enterprise', 'enterprise-team', 'Request body'), providing no additional meaning. The tool description adds no semantic value for parameters. For a complex bulk operation with a nested body parameter, the agent needs much more detail about expected structure and values.

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 'Remove organization assignments' clearly states the action and resource. It distinguishes from sibling tools like 'github_enterprise_team_organizations_add' or 'bulk_add' by indicating removal. However, it could be more specific about what is being removed (e.g., organization assignments from the enterprise team).

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. It does not mention prerequisites, context, or exclusions. The agent has no information about appropriate scenarios for bulk removal compared to individual deletion.

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