Remove Model From Group

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

With no annotations, the description correctly carries the responsibility: it reveals the operation is non-destructive to the model ('model itself is not deleted', 'leaves the model untouched') and exposes the API limitation on systems. It doesn't cover failure modes or permission requirements, but for this simple mutation the key behavioral risk is addressed.

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?

Two tight paragraphs, first sentence front-loads the action and scope, and each further sentence earns its place by explaining a limitation or non-deletion guarantee. No padding.

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?

The core behavior and limitations are covered and an output schema exists, so return values needn't be described. Missing semantics for the required server_version parameter is the main gap, and there's no note about error behavior when the model is not in the tag, so completeness is short of excellent.

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 meaning beyond the schema by clarifying tag_id refers to a tag group (tags only, not systems) and that model_id refers to a model whose removal will not delete it. However, the required server_version parameter is left undocumented in both schema and description, so it is not fully explained.

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?

States a specific verb and resource: 'Remove a model from a tag group', and immediately clarifies the model is not deleted. It also contrasts with add_model_to_group by emphasizing tag-only removal, so it is not confused with system-group operations.

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?

Explicitly says removal is supported for tags only and systems have no remove-member endpoint, so the agent knows not to use this tool for system membership. Also explains that a model added via add_model_to_group(kind='system') cannot be detached, giving a concrete when-not scenario.

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