github_orgs_revoke_org_role_team

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

No annotations are present, so the description must disclose behavioral traits. It only states 'Remove an organization role' without mentioning permissions required, reversibility, side effects, or any other behavioral details. The description is too minimal to provide transparency.

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, front-loaded with the action and resource. It is concise with no wasted words, though it could be slightly more informative in the same length.

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 and absence of output schema, the description is minimally adequate. It explains what the tool does but lacks context about effects, reversibility, or any post-removal state. For a basic removal tool, it is incomplete but not severely lacking.

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 description coverage is 100% (each parameter has a description, though they are just the parameter names repeated). The description adds no additional meaning beyond the schema. Baseline is 3 due to high coverage, but no extra value.

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 an organization role from a team' clearly states the specific action (Remove), the resource (organization role), and the target (team). It distinguishes itself from sibling tools like github_orgs_revoke_all_org_roles_team (which revokes all roles) and github_orgs_assign_team_to_org_role (assigns).

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 vs alternatives, no prerequisites, and no context on when not to use it. It is a standalone sentence without usage advice.

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