bundle_ids_delete_instance

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

No annotations are provided, so the description carries the full burden, yet it discloses nothing beyond the HTTP method: no destructive-effect warning, no confirmation that the deletion is permanent or cascading, no auth/permission requirements, no response behavior. For a deletion tool this is a serious gap.

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?

It is very short and front-loaded, but the sentence is literally duplicated in parentheses, which is pure waste rather than useful brevity.

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 destructive, unannotated delete operation with no output schema, the description should at minimum state permanence, side effects, and failure conditions. None of that is present, leaving the agent under-informed for a risky call.

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 100% for the single 'id' parameter and the schema already explains it as 'the id of the requested resource'. The description adds no syntax, format, or sourcing detail beyond the route template, so the schema does all the work.

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 does name a specific verb and resource (DELETE on a bundleIds resource identified by id), so the agent knows roughly what it does. However, it is essentially the REST route restated with no explanation of what a bundle ID is or how this differs from siblings like bundle_ids_update_instance or bundle_ids_get_instance.

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?

There is no guidance on when to use this versus alternatives, no prerequisites, and no warning that deleting a bundle ID is a destructive operation that may affect associated profiles and capabilities. The only cue is the word DELETE in the route string.

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