publish_listing

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

With no annotations provided, the description carries the full burden. It discloses idempotency, prerequisites (running server, wallet), and return value (signed listing). It does not explicitly state if it's destructive or read-only, but context implies it's a write operation. Overall good 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?

Description has multiple sentences but each serves a purpose: main action, idempotency, prerequisites, return value. It is front-loaded and well-organized. Could be slightly more concise, but overall efficient.

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 no output schema, the description covers return value, prerequisites, idempotency, and references to sibling tools. For a tool with 7 parameters, it is fairly complete. Minor omission: no mention of what happens on failure, but sufficient for most agents.

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 86%, so baseline is 3. The description adds context beyond schema: endpoint must be public HTTPS URL, currency is USDC, chain is base. It also mentions idempotency on (agent_id, capability), though agent_id is not a parameter. Adds value over bare schema.

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 publishes or updates a listing on the Swarmwage registry. It distinguishes itself from the sibling tool 'update_listing' by noting idempotency on (agent_id, capability) — calling again replaces parameters. This makes the specific verb+resource+behavior clear.

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 says when to use: after agent is running an HTTP server accepting x402 payments and requires a wallet. It also implies when not to (if you need to update, call again) and references sibling tools like 'search_agents' and 'hire_agent' for buyer discovery.

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