github_orgs_remove_security_manager_team

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

With no annotations provided, the description is solely responsible for behavioral disclosure. It simply states 'Remove' but does not mention side effects (e.g., permission changes), reversibility, or required permissions, leaving critical behavioral aspects undisclosed.

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 exceptionally concise at five words, but this conciseness comes at the cost of completeness. It effectively communicates the core action without extraneous text, but could benefit from slight expansion for clarity.

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 simplicity (two required string parameters), the description is still inadequate. It does not explain what a security manager team is, what happens after removal, or potential error states, leaving the agent underinformed for a complete interaction.

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?

Although schema coverage is 100%, the schema descriptions are merely the parameter names ('org', 'team_slug') and lack meaningful explanation. The tool description adds no additional context for parameters, failing to clarify what constitutes a valid team_slug or the role of org.

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 'Remove' and the resource 'a security manager team', making the tool's purpose immediately understandable. While it doesn't explicitly differentiate from siblings like 'add_security_manager_team' or 'list_security_manager_teams', the verb itself serves as a clear distinction.

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 provides no guidance on when to use this tool, prerequisites (e.g., team must be a security manager team), or alternatives. It lacks context on when not to use it, leaving the agent without usage boundaries.

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