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

With no annotations, the description carries the full burden and does well: it explains that prepaid balance covering reward plus 20% fee means instant publish, otherwise a checkout_url is returned for a human to pay. It also discloses that prohibited categories are rejected. It omits auth/account prerequisites and what the rejection path looks like (error vs. silent refusal).

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?

Four tight sentences: purpose first, then payment behavior, then the funding escape hatch, then the use/exclusion boundary. No filler and nothing repeated for its own sake.

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 10-parameter creation tool with a nested details object and no output schema, the description covers the key outcome (instant publish vs. checkout_url) that an agent needs to interpret the result. Location, template, and field-level semantics are left entirely to the 100%-covered schema, which is reasonable but leaves the description thin on the required lat/lng conditionality.

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 100%, so the baseline is 3, and the description largely restates what the schema already declares about reward_usd fee math and funding modes. It adds a little framing on how funding choice affects flow, but no new syntax or format detail beyond the 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 opening sentence states a specific verb and resource ('Post a paid real-world quest'), plus the audience ('verified human quester') and the geographic scoping. It is unmistakably distinct from siblings like get_quest, list_quests, approve_quest, and cancel_quest.

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 positive use case ('tasks only a person on site can do') and an explicit exclusion list (account creation, social posting, reviews, CAPTCHAs, illegal work), plus a funding-mode alternative ('use funding: balance to fail instead'). It does not name sibling tools it routes to, though the template enum in the schema points at list_templates.

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