update_listing

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

Without annotations, the description carries the full burden. It states idempotency and the upsert nature, but fails to disclose side effects, return values, error conditions, or the meaning of 'wallet requirement'. Basic transparency but lacks depth.

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?

Two sentences with no waste. The first establishes the relationship to `publish_listing` and idempotency; the second provides the use case and a key prerequisite.

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 description is too brief given the tool's complexity: 7 parameters, no output schema, no annotations. It omits parameter semantics for 4 parameters, does not describe return values or error behavior, and only mentions the wallet requirement without details.

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?

With only 14% schema coverage, the description adds value by naming three parameters (price, endpoint, max_latency_ms) but omits explanation for `capability` and `first_call_free`, and does not compensate for the low coverage of other parameters like `currency` (though enum) and `chain` (described in schema). The required parameter `capability` is not clarified as the listing identifier.

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 it is an alias of `publish_listing` and an idempotent upsert for updating existing listings, distinguishing it from siblings like `publish_listing` (for new listings) and `list_my_listings` (for listing owned listings).

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 explicitly advises using this tool when changing price, endpoint, or max_latency_ms of an already published capability, and mentions the wallet requirement. However, it does not explicitly state when not to use it or list alternatives beyond being an alias.

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