github_enterprise_team_memberships_remove

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

No annotations provided, so the description must disclose behavioral traits. It only says 'Remove team membership' without indicating destructiveness, auth requirements, or side effects. The name implies mutation, but no further details are given.

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 short (one phrase), which is concise but at the expense of clarity. It is front-loaded but lacks necessary detail to be useful. It could be expanded while remaining terse.

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 three required parameters, no output schema, and no annotations, the description is very incomplete. It does not explain what the tool does in detail, what parameters are for, or any constraints or side effects. More contextual information is needed for correct use.

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?

Input schema has three required parameters with descriptions that are just the parameter names ('enterprise', 'enterprise-team', 'username'). The description does not add any meaning or context beyond the schema. Schema coverage is 100% but descriptions are tautological and unhelpful.

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 team membership' clearly states the action (remove) and the resource (team membership). The tool name includes 'enterprise_team_memberships', so the scope is implied. It distinguishes from sibling tools like 'add' or 'bulk_remove' but lacks specificity about what is being removed (a user's membership in an 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 like bulk removal or adding memberships. Sibling tools exist but are not mentioned. The description does not provide context for appropriate usage scenarios.

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