delete_offer

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

With no annotations provided, the description carries the full burden. It explicitly discloses destructive behavior ('Permanently delete'), ownership requirement ('your own offer'), and an important business rule ('Blocked if the offer has active trades'). This goes beyond minimal requirements, though it could be richer (e.g., effects on linked data).

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?

One sentence, highly compact, front-loaded with the action and key qualifiers. No fluff or redundant details.

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?

The tool has only 2 params and no output schema, so the description is largely adequate. It covers the essential behavior and a key blocking condition. It does not mention return values or other failure modes, but these are not critical for a simple delete operation. Overall, it is sufficiently complete for an agent to select and invoke correctly.

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?

Since the input schema already provides 100% parameter descriptions, the baseline is 3. The description does not add new parameter-level detail; 'your own offer' is already reflected in the schema's userId description. No additional context is provided.

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 verb and resource: 'delete your own offer.' It also specifies permanence ('Permanently') and a condition ('Blocked if the offer has active trades'), which distinguishes it from related tools like delist_offer.

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 provides clear context on when to use this tool: for permanent deletion of one's own offer, with the caveat that it cannot be used when trades are active. However, it does not explicitly mention alternatives or exclusions, so it stops short of a 5.

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