balena_remove_organization_member

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the destructive nature is covered. The description adds a small behavioral detail: it removes exactly one membership, not a range or all memberships. However, it does not disclose consequences such as permanence or downstream effects, though the confirm parameter in the schema partially compensates.

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?

A single, direct sentence that is front-loaded with the core action and scope. There is no filler or redundant wording, and it earns its place by clarifying exactly what is removed.

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?

For a simple delete-by-ID operation, the description plus annotations and confirm schema cover the essentials: what is removed, how to identify it, and that confirmation is required. It could mention how to obtain the membership ID (e.g., via balena_list_organization_memberships), but this is not critical for invoking 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 description gives meaning to membership_id by calling it a 'numeric membership ID', which is somewhat redundant with the schema's property name but helpful. It does not explain the confirm parameter, though the schema already provides a clear description for it. With 50% schema coverage, the description adds just enough context for membership_id.

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 uses a specific verb ('Remove'), a precise resource ('organization membership'), and a scoping method ('by numeric membership ID'). It clearly distinguishes this from sibling tools like balena_remove_team_member, which operates on a different resource.

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 states what the tool does but gives no guidance on when to choose it over alternatives, such as balena_add_organization_member or balena_list_organization_memberships. There are no preconditions, exclusions, or references to related tools.

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