builds_beta_groups_delete_to_many_relationship

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

No annotations are provided, so the description carries the full disclosure burden and does not meet it. It implies removal via the DELETE verb but says nothing about whether this is destructive, whether all listed linkages are removed at once, permission requirements, or reversibility.

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 text is short, but the path is duplicated verbatim in parentheses, which is pure waste, and the 'see OpenAPI components.schemas...' pointer is not self-contained information for an agent.

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 nested-body mutation tool with no annotations and no output schema, the description omits the operation's semantic effect and consequences entirely. The schema covers the parameters, but the description leaves the agent without enough context to invoke this safely.

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 description coverage is 100%, so the schema already documents 'id' and the body. The description only points at an external OpenAPI component for the body shape, adding a reference but no meaning beyond what the schema field description already says.

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 is a mechanical restatement of the tool name as a URL: 'DELETE /v1/builds/{id}/relationships/betaGroups', repeated twice. It never states in plain language that it removes beta groups from a build, nor distinguishes it from the sibling builds_beta_groups_create_to_many_relationship.

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 versus the create/replace relationship siblings, no prerequisites, no mention of what state is required for the call to succeed. The agent gets only the HTTP verb.

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