delete_market

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

No annotations are provided, so the description carries full responsibility. It only states the action without disclosing irreversibility, permission requirements, cascading effects, or response behavior. The verb 'delete' implies destruction, but that's the purpose, not behavioral 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 concise sentence with no extraneous words. It front-loads the essential information. However, its brevity borders on under-specification, trading detail for concision.

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 the context of many sibling tools and no output schema, the description is incomplete. It doesn't explain return values, error conditions, or consequences. For a destructive operation, more detail is needed.

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 schema already documents the single 'id' parameter with the description 'Market ID to delete', achieving 100% coverage. The tool description adds no additional parameter semantics or format expectations. Baseline 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 'Delete a market' states a clear verb and resource, distinguishing it from sibling market tools like get_market, create_market, and update_market. The purpose is unambiguous. However, it doesn't elaborate on scope or any special conditions, so it's clear but minimal.

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 usage guidance is provided. The description does not mention prerequisites, when to use this tool versus other delete_* tools, or any side effects. Sibling tools like delete_collection, delete_product, etc., are indistinguishable in terms of usage context.

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