delete_bidder

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

With no annotations provided, the description alone must disclose behavioral traits. 'Delete a bidder' merely restates the action and implies destructiveness but does not explain irreversibility, cascade effects, required permissions, or error conditions. This provides no information beyond the tool's name.

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 extremely short (three words) and free of unnecessary content, but it is so under-specified that it lacks meaningful structure. While concise, it does not enrich the tool with contextual details that would justify a higher score.

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?

Given it is a destructive operation with no annotations and no output schema, the description should at least mention the permanent nature of deletion or success/error behavior. 'Delete a bidder' is minimally complete for a trivial CRUD action but omits crucial contextual details about side effects, leaving the agent at risk of using it inadvertently.

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 fully describes the single parameter `id` as 'Bidder ID', so schema coverage is 100%. The description adds no new parameter information, but since the schema is self-explanatory, the baseline score of 3 is appropriate.

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 clearly states the action ('Delete') and the resource ('a bidder'), using a specific verb that distinguishes it from sibling tools like get_bidder, update_bidder, and create_bidder. It is concise and unambiguous, though it lacks any additional scope or nuance.

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 is provided on when to use this tool versus alternatives, prerequisites, or consequences. It simply states the action without mentioning that deletion is permanent or that it should only be used when a bidder is no longer needed, leaving the agent to infer appropriate usage.

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