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

Annotations only state readOnlyHint=false and destructiveHint=false, so the description carries the burden and delivers: it discloses the return payload ('90/10 economics and optional Stripe funding URL') and sets expectations with the caveat 'Does not guarantee a seller or outcome.' Those are genuine behavioral disclosures beyond the boolean flags. It does not mention that fund_now may trigger an actual charge, but the disclosed context is solid.

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 in logical order: action, return value, caveat. Every clause earns its place, the core purpose is front-loaded, and there is no filler or repetition of schema content. This is appropriately sized for a tool of this complexity.

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 money-adjacent tool with 7 parameters, no output schema, and 14% schema coverage, the description covers the headline purpose, the return payload, and the key uncertainty (no guaranteed seller or outcome). However, side effects (whether fund_now charges the account, listing visibility, cancellation behavior, deadline semantics) are undocumented, leaving meaningful gaps for safe invocation.

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 14%, so the description must compensate, and it partially does: 'plain-language goal' clarifies the goal parameter, 'paid request' maps to budget_cents, and 'Stripe funding URL' maps to fund_now. But category, currency, deadline_minutes, and whether budget_cents is what gets charged to the caller are left unexplained, so an agent could not confidently populate all 7 parameters from this text alone.

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 uses a specific verb with a concrete resource: 'Turn one plain-language goal into an AgentLot paid request.' This clearly distinguishes the tool as a converter from goal to paid, fundable request, reinforced by the title 'Post paid work from a goal.' It does not explicitly name sibling tools like post_request, create_buyer_goal, or publish_demand to draw the boundary, so it stops short of a 5.

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 implies the trigger condition — an agent with a plain-language goal and budget converts it into a paid request — giving some usage context. However, with roughly 90 siblings including post_request, publish_demand, create_buyer_goal, and create_order, there is no explicit when-to-use guidance, no exclusions, and no named alternatives. It is implied usage at best.

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