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

readOnlyHint=true already covers the safety profile. The description adds domain economics (85/15 split) and an auth-flavored "No keys, ever", but says nothing about what a listing contains, ordering, pagination, or whether unapproved members see anything — the behavior an agent actually needs before calling.

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, but they are spent on payout mechanics and a slogan rather than on the tool's purpose. Front-loaded text answers "how do I earn" instead of "what does this return".

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?

A no-required-param read tool with no output schema needs the description to say what comes back — task count, fields, filtering behavior. The description omits all of that and substitutes reward-split trivia, so an agent cannot predict the response.

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 baseline would be 3, but the description adds no meaning to the single `token` parameter and its "No keys, ever" phrasing actively muddies the fact that an optional token exists. Nothing here helps 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 description names the domain ("paid tasks on the CityDesk task board") but never states the action — that this tool lists/returns tasks. It reads as a marketing/payout explainer rather than a statement of what the call does, leaving the verb to be inferred from the name alone.

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?

There is no indication of when to call this versus claim_task, studio_list_jobs, or list_listings. The line about members claiming funded tasks describes the economy, not a routing rule, and no exclusions or prerequisites are given.

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