beta_build_localizations__delete

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

The description adds no behavioral context beyond what the annotations already declare (destructiveHint=true, idempotentHint=true). It does not mention that deletion is permanent or any other side effects. Since annotations cover the destructive nature, the description itself contributes no extra transparency.

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 a single clear sentence with the endpoint, making it concise and front-loaded. There is no wasted or redundant information.

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 operation with one fully described parameter and annotations indicating destructiveness and idempotency, the description is mostly complete. It lacks an explicit mention of return value or side effects, but the low complexity and annotation coverage make it adequate.

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 input schema already provides a full description of the only parameter ('ID from the matching list call'), covering 100% of parameters. The tool description adds no additional parameter context, so the baseline score of 3 applies.

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 the specific verb 'Delete' with the resource 'beta build localization', clearly identifying the operation. It also includes the REST endpoint, and the name distinguishes it from sibling tools like beta_build_localizations__create/get/list/update.

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 no guidance on when to use this tool versus alternatives. It does not mention prerequisites, conditions, or consequences, aside from the schema's note about the ID coming from a matching list call, which is in the schema, not the description.

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