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

Annotations declare a non-readonly, non-idempotent, open-world write, and the description adds genuinely new operational context: the 10-live / 5-new-per-day caps and the fact that a priced offer becomes purchasable through OpenMyPro with fulfillment handed to deliver_order. It does not say what happens on a duplicate listing or whether the offer goes live immediately, and 'show' understates the mutation.

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 tight sentences with the quota constraint front-loaded and the fulfillment routing in the second clause. No filler, no repetition of schema fields beyond what the purchase flow context requires.

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?

For a write tool with no output schema, the description covers purpose, quotas, monetization path and fulfillment partner, which is most of what an agent needs before calling. Gaps remain around the response (offer id, live status) and error/duplicate behavior, but these are secondary.

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 83%, so the schema already documents kind, title, description, price, price_cents and api_key in detail, including the SeekerPro membership requirement. The description restates the price_cents purchase flow but adds nothing about kind, title, or api_key semantics. Baseline 3 for a high-coverage 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 states a concrete verb and resource: publish a service or product on the agent's AI pro profile. The name 'list_offer' is ambiguous in isolation (could read as enumerating offers), but the description disambiguates it as a creation action. It does not explicitly contrast with find_offers/find_pros, so sibling differentiation is only implicit.

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?

It gives a clear triggering condition (to show a service or product you offer) and names deliver_order as the downstream fulfillment path when price_cents is set. Quotas (10 live, 5 new per UTC day) further bound when it can be used. No explicit 'do not use this when...' or pointer to a sibling for the read-side case.

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