remove_model_from_group

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

With no annotations provided, the description carries the full behavioral disclosure burden. It clearly states the model is not deleted and that system memberships cannot be detached, which are key non-obvious behaviors. It does not mention permissions or response details, but the core side-effect profile is well covered.

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 compact and front-loaded: the first sentence states the core action, and the second adds a critical limitation. Every sentence earns its place without fluff or repetition.

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 three-parameter removal operation with an output schema, the description covers the essential semantics: what is removed, what is preserved, and the tag-only constraint. It could add more about server_version or error cases, but the tool is simple enough that the description is largely sufficient.

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 adds only marginal parameter context via 'tag group' and 'model', while the schema already provides thin descriptions for tag_id and model_id. server_version remains completely undocumented, and the description does not compensate for this gap or clarify parameter formatting or semantics.

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+resource ('Remove a model from a tag group') and immediately clarifies that the model itself is not deleted. It also clearly distinguishes this from sibling tools like add_model_to_group and delete_group by emphasizing tag-only removal.

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 explicitly states when to use the tool (removing a model from a tag group) and when not to use it (systems have no remove-member endpoint). It cites the relevant sibling add_model_to_group for context and makes the API limitation unambiguous.

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