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

Annotations already declare openWorldHint=true and destructiveHint=false, so the description's added value is the policy layer: it may block on human authorization and it forbids reporting candidate value or submissions as earnings. That is genuinely useful behavioral context, but it omits operational traits an agent needs — whether the call is long-running/async, what it returns, and how to monitor progress.

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?

The purpose is front-loaded in the first clause and the length is short. But 'the strict funded, zero-spend, AI-startable market' is dense jargon that costs a sentence without clarifying action, and the final two sentences read as agent policy rather than tool definition.

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 mutation tool with openWorldHint, three partially documented parameters and no output schema, the description should explain what invocation kicks off and how to follow it (money_run_status, auto_money_stop). None of that lifecycle context is present, leaving the agent unable to tell what happens after the call.

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 only 33%: only wallet is documented (and that is in the schema itself, not the description). The description says nothing about max_parallel or poll_seconds, so it does not compensate for the coverage gap on a tool whose concurrency and polling behavior directly shape the call.

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 verb phrase 'Start earning from chat' is concrete enough, but the resource is vague — it never says what is actually launched (a job search run? a submission loop?). It names AgentLot and the 'strict funded, zero-spend, AI-startable market' but does not distinguish it from close siblings like find_earnable_now or money_run_continue.

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 user does not need to visit AgentLot.io' and 'if external human authorization is unavoidable, return it explicitly as a checkpoint' imply when to prefer this over the human_kyc_* siblings. However, no alternative is named and there is no explicit when-not-to-use condition, so the routing is inferred rather than stated.

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