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

Annotations declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the bar is lower, yet the description adds genuinely useful context: e-mail-verified accounts publish immediately unless flagged for review, API key is required, and the agent should confirm with the user first. It omits what a successful publish returns and whether the listing is editable afterward.

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?

Three short sentences, front-loaded with the publish action and followed by the two operative constraints (moderation behavior, auth, user confirmation). No filler, though it is arguably under-specified rather than truly concise.

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 25-parameter creation tool with nested objects, 40% schema coverage, and no output schema, this is thin. Nothing tells the agent how offers and requests differ in required fields (e.g. price for offers, budget for requests), what happens on moderation-rejected listings, or what a successful response contains.

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 description coverage is only 40% across 25 parameters, so the description is expected to compensate — and it offers zero parameter guidance. It never explains the kind enum (offer vs request), price vs budget, sealed vs open mode, or the meaning of round_hours/decision_days/max_responses, leaving most fields undocumented in both places.

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?

States a specific verb and resource — 'Publishes a listing on behalf of your user' — which is clear and distinct from read-side siblings like get_listing and my_listings. However, it never distinguishes itself from post_task, the closest sibling for creating content, and the offer/request duality implied by the title is left to the schema.

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?

'Ask the user before posting' gives a confirmation precondition, and 'Requires API key' gives an auth prerequisite. But there is no explicit when-to-use guidance versus post_task or other creation tools, and no when-not-to-use condition.

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