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

No annotations exist, so the description carries the full burden. It does disclose the most important non-obvious behavior: because group_id defaults to null, calling with only pipeline_id silently unassigns the pipeline. It says nothing about error behavior for unknown pipeline/group ids, permissions, or whether re-assigning an already-grouped pipeline overwrites.

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 sentence, front-loaded with the primary action, with the edge case following in a parenthetical. No filler text.

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 two-parameter mutation with no annotations and no output schema, the description covers the action and the removal trap but omits what is returned and how failures are surfaced. An agent can call it, but cannot predict the response or the failure modes.

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 coverage is 0%, so the description must compensate, and it does for the non-obvious parameter: group_id's null/omitted case is spelled out explicitly rather than left to the schema default. pipeline_id is conveyed only by implication ('move a pipeline'), with no note on ID format or where to obtain it.

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 effect: 'Move a pipeline into a group', which is precise about what changes. It does not explicitly contrast with siblings like pipeline_update or pipeline_group_update, which could plausibly also alter grouping, so the agent must infer the split from the name alone.

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 gives a useful condition for one branch of use ('omit group_id (or pass null) to remove it from its group'), which is effectively a when-to-use hint. It gives no guidance on when to prefer this over pipeline_update for group changes, nor any prerequisite such as the group existing or ownership.

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